when clicked on clean/disinfect CIS deletes the file. if CIS cannot clean/disinfect the files it should say so then the user can decide to quarantine or ignore the files. clean/disinfect deletes the file. this function will remain this way or its going to change like i mentioned.
But aren’t clean and disinfect two different things?
I’m not using version 4 yet, but in the videos I’ve watched, these appear to be different selections in the dropdown menu.
Or are you saying both functions have the same result?
If so, in the interests of false positives, I agree that if the file cannot be fixed, the user should be able to intervene before the file is wiped from the system.
yes both the functions have the same results. both the functions deletes the file. i think disinfect if fail to fix the file should give an option to quarantine/delete/ignore and the word clean should be changed to delete. the word clean is confusing if clean means deleting the files.
I don’t understand how you can talk about this being so calm? This is freakin’ ridiculous!!! The button says Clean and it deletes files. You pick “manually” Disinfect… and it deletes files! What the hell is this, I ask! A double mockery. Unauthorized file deltion!
wow! that’s bad!! 100% support to what Bucic had to say! :-TU
All I can add to this is that in v4.1 Melih said that cleaning/disinfection will be much better; he calls it acid like cleaning.
Sounds like it already has acid like cleaning.
And when will it be released? I wrote a monkey-instruction for Comodo for someone… not very IT and I had to recommend disabling Sandbox and explain that no matter what you choose on virus detection the file will be deleted. Unless ignored of course. Not exactly the kind of message Comodo would like to send to new users, I presume.
Terminology, maybe not appropriate, is one thing, reality is another.
How would any of you suppose that whatever software is able to “clean” a file? Maybe possible with some added data to a data file (e.g. Microsoft Word macros), but what about some dll or executable?
No software knows how to repair files of which it must be reminded that they are often hard-coded and copyrighted.
In these conditions, the only possible behavior is previous backup of the said files, and i remember that, speaking e.g. of windows XP, malicious contents also contaminate windows restore: you backup and restore sh…
The eventuality of some modern and working kind of sandbox, where all the “safe files” would be protected, would be a solution, but is not realistic unless one uses real-time backups on a different physical media.
This kind of technique, even if not using heavy hardware raid procedures, already exists, and supposes one has at least a full daily backup on two different destinations, in the same time he has protected rescue media.
Waiting for some hypothetic and utopic software to be able to proceed to automatic cleaning, the answer is clear: never allow whatever software to quarantine, clean, or delete whatever, knowing that you should not place yourself in a position in which this becomes an emergency, but letting you time to, manually, think by yourself about what you actually should delete.
currently CAV doesn’t have the ability to disinfect any file which had been previously infected by sality virus(for example) ! …
I think that will come later and it needs really good time to come out … so be patient gentlemen , believe me it worths to wait
It’s not about the philosophy of disinfection possibilities nor about thanksgiving for what may come but the fact that COMODO is exposing even more experienced users to unauthorized file deletion. Simple as that and no-thing more. Regarding this particular bogus COMODO is already behind the point where it could get decent from this situation. But as they say “it’s never too late” - so to save the last bits of decency COMODO should rename the buttons until a proper mechanism of disinfection/information on disinfection failure is introduced.
And no - software being freeware nor software being great in other aspects is an excuse for inflicting data loss.