The following added to the firefox profile would be enough to 'fix' this bug:
/usr/bin/clamscan Ux,
However, Ubuntu ships a profile for /usr/sbin/clamd. It would be much better if the plugin could (optionally?) use clamd by reading in the contents of the file to be scanned, then opening /var/run/clamav/clamd.ctl and writing:
SCAN <complete file contents>\n
Then checking for the output text/return code. This would allow for us to use in the firefox profile:
/var/run/clamav/clamd.ctl w,
This allows for better security since clamscan won't be an avenue of attack.
The following added to the firefox profile would be enough to 'fix' this bug:
/usr/bin/clamscan Ux,
However, Ubuntu ships a profile for /usr/sbin/clamd. It would be much better if the plugin could (optionally?) use clamd by reading in the contents of the file to be scanned, then opening /var/run/ clamav/ clamd.ctl and writing:
SCAN <complete file contents>\n
Then checking for the output text/return code. This would allow for us to use in the firefox profile: run/clamav/ clamd.ctl w,
/var/
This allows for better security since clamscan won't be an avenue of attack.