ClamAV version: ClamAV 1.0.5/27420/Mon Oct 7 08:43:46 2024
OS: Debian 11
So it looks like file names are processed differently when they are specified directly on the command line vs when they are specified in the --file-list file. I would really appreciate any suggestions on how to make the behavior consistent when special characters are present. Thank you.
I encountered an issue trying to use
clamdscan
with--file-list
option when one of the files I want to scan has special characters in the name.Test file name:
'test'$'\n\n''SHUTDOWN'$'\n''.py'
, located in the/temp/
folder.This works:
This does not work:
Environment info:
ClamAV 1.0.5/27420/Mon Oct 7 08:43:46 2024
So it looks like file names are processed differently when they are specified directly on the command line vs when they are specified in the --file-list file. I would really appreciate any suggestions on how to make the behavior consistent when special characters are present. Thank you.