Hi there SeaFile team,
Just a quick feedback concerning the ClamAV sidecar container integration. It’s been working really good to be honest and I’ve scanned my complete storage which revealed many triggering files (a massive amount being false positive, EICAR txt entries etc etc…). In any cases, triggering bits has nothing to do with SeaFile iteself.
In regards to SeaFile though, a couple of items may need some tunning:
- the “Virus Scan” page within “System Admin” seems to be single paged in regards to html renderings – which means that on many triggering samples, the overall handling is a bit painful, you’ve got the do them one by one as while the complete listing would need more than one page to display in full, it seems you cannot apply “delete OR ignore” on all of the currently displayed list.
- I would tend to think that as any given samples may trigger a specific ClamAV signature, that information could be part of the “Virus Scan” report page, that may help at finding false positives etc etc.
- Last point, the triggering “file” is named “Virus File”, I’d rename that to “Infected File”.
Let me know,
If you’d need any access to my rig to check the behaviors, just let me know.
Kind regards,
m.