CLAMBC(1)

πŸ’– CLAMBC(1) β€” the Clam AntiVirus bestie files πŸ’–

okay so bestie, welcome to clambc, aka the Bytecode Analysis and Testing Tool from the Clam AntiVirus fam. she's the girl who lets you poke at bytecode signatures and see how they perform. let's get into it πŸ’…


✨ SYNOPSIS ✨

clambc <file> [function] [param1 ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

so. bytecode signatures are a platform independent executable plugin format that extend ClamAV's malware detection capabilities. that's the whole vibe β€” little plugins that make ClamAV see more malware. 🫢

this tool exists for signature authors and ClamAV developers to test bytecode signatures and to test bytecode runtime performance. iykyk.

Caution: You should NEVER run bytecode signatures from untrusted sources. Doing so may result in arbitrary code execution. not me being dramatic, that is literally what the manpage says. do not do it. periodt. πŸ’€

🌸 OPTIONS 🌸

  • --help, -h β€” Show help. your girl's got your back when you forget stuff πŸŽ€
  • --version, -V β€” Show version. just the numbers, no notes ✨
  • --debug β€” Show debug. all the messy details, out loud πŸ™ˆ
  • --force-interpreter, -f β€” Force using the interpreter instead of the JIT. no speedrunning today, we're doing it the long way πŸ’…
  • --trust-bytecode, -t β€” Trust loaded bytecode (default yes). bestie trust is default-on, but you can turn it off if you're feeling suspicious πŸ‘‘
  • --info, -i β€” Print information about bytecode. gossip about the bytecode, basically πŸ“
  • --printsrc, -p β€” Print bytecode source. show me the receipts πŸ“œ
  • --printbcir, -c β€” Print IR of bytecode signature. the intermediate representation, lowkey the main character 🧚
  • --input, -r β€” Input file to run the bytecode on. gotta feed her something 🌈
  • --trace <level>, -T β€” Set bytecode trace level 0..7 (default 7). yes, 0 through 7, and yes, the default is the max. she's chatty fr fr πŸ”₯
  • --no-trace-showsource β€” Don't show source line during tracing. for when the tracing is giving too much πŸ’€
  • --statistics=bytecode β€” Collect and print bytecode execution statistics. numbers, we love numbers ⭐
  • file β€” File to test. the whole point, honestly πŸ’œ

πŸ’– CREDITS πŸ’–

Please check the full documentation for credits. they said it, not me 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Tomasz Kojm <tkojm@clamav.net>, Kevin Lin <klin@sourcefire.com>


🌟 SEE ALSO 🌟

clamscan(1), sigtool(1)


and that's the whole page, bestie!! this was ClamAV 1.5.4, dated September 2014, and it slayed in the most CLAMBC(1) way possible. go forth and test responsibly (and never ever run untrusted bytecode, i'm begging) πŸ’…βœ¨πŸŽ€