Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infected files not appearing in quarantine #10

Closed
GoogleCodeExporter opened this issue Apr 23, 2016 · 3 comments
Closed

Infected files not appearing in quarantine #10

GoogleCodeExporter opened this issue Apr 23, 2016 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Scheduled nightly scan
2. Open history for scan after it runs (my history says it found 51 infected 
files)
3. go to quarantine to remove files... there are none!

What is the expected output? What do you see instead?
I had expected 51 files in the quarantine... and there are none.

What version of the product are you using? On what operating system?
5.04 of clamtk - ubuntu 12.04


Please provide any additional information below.
Not much further to add... just that perhaps there is a setting that I'm not 
finding that is the option to "Put infected files in Quarantine?" or something 
like that

Thanks!

Original issue reported on code.google.com by jhh...@gmail.com on 8 Mar 2014 at 4:43

@GoogleCodeExporter
Copy link
Author

Also ... I just noticed it doesn't seem to be saving my scheduled scan 
properly.  Every time I go to look at the scheduled scan it shows that it's 
scheduled for 0 hour - minute, and the definitions file update is schduled for 
hour 9 minute 16. 

And as a feature request it would be nice to define the directory it starts the 
scheduled scan from ... not just the home directory.

Having said all that, I don't want to sound like I'm only complaining ... I 
appreciate tremendously the effort put into this (I'm also a programmer) 

Original comment by jhh...@gmail.com on 8 Mar 2014 at 4:48

@GoogleCodeExporter
Copy link
Author

Hi,

Thanks for letting me know.

1. You are correct - there is no auto-quarantine or auto-delete (anymore). I 
removed it after realizing how dangerous (in a geek way) it can be.  For 
example, I didn't consider that most email boxes (on *nix) are a single flat 
file.  Guess what happens if it pops for malware or a PUA?  The whole file - 
your inbox - is gone.  Anyhoo, while I agree we need a better solution if 
something pops during a scheduled scan, I do not like the 
auto-{quarantine,delete} at all...  Maybe something on startup?  Not sure.
2. Can you elaborate on the scheduled part not working properly? What are you 
setting it to, and what does it save it as?
3. The 4.xx series had a choice between scanning home directories or at the 
root.  Really, ClamAV (and thus ClamTk) are more for scanning individual files 
than in the way a Windows system works.  In the 5.xx series I tried to force 
this ( :) ) mentality by showing only the home directory.  
4. Doesn't sound like complaining - I appreciate the feedback.

respectfully
Dave M

Original comment by dave.n...@gmail.com on 8 Mar 2014 at 11:26

@GoogleCodeExporter
Copy link
Author

Original comment by dave.n...@gmail.com on 16 Mar 2014 at 3:59

  • Changed state: WontFix

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant