I do not get why would you want to secure delete a malicious file…it is has nothing to do with your privacy as long as it has done no damage to your system/not transfer of important data out of the system.
If the file in question is a false positive, than you would still want the file…so what is the use of secure delete?
If you are worried about the malicious file being restored to allow re-infection to take place, it is very likely that direct access to the machine by the malicious actor is required to even allow that to happen.
Besides, when that happens, you would have much more important stuff in plain text to worry about rather than the possibility that a malicious file gets restored!
You should have realized by now that the more you answer this trawler,
the more he/she will come back with other useless information to continue
his/her quest to annoy us.
Ignore and allow him/her to simply have a conversation with him/her self. ;D
We know that, which is why I said avast doesn’t do multiple overwrites and doesn’t really need to.
We know that it is removed from the FAT but the data remains and the space is marked as free so in due course will be overwritten.
Files in the chest are:
renamed so they aren’t the same as the original.
they are encrypted.
So there is no linkage to the original and deletion is from the chest and is for the file in its encrypted state.
I honestly don’t see the need for a secure deletion of files deleted from the chest. Who is going to be trying to restore the file and for what purpose ?
This is an overhead for a problem that really isn’t there (point 1 & 2 above), I certainly wouldn’t want that feature, it is bloat.