LWN.net Logo

Does this not handle unsafe overwrites?

Does this not handle unsafe overwrites?

Posted Dec 7, 2006 23:22 UTC (Thu) by droundy (subscriber, #4559)
Parent article: Secure deletion and trash bin support

It sounds like this patch doesn't handle the "secure" files in the case where their contents may be modified. In that case, the old contents could end up being left around on disk somewhere (e.g. if I run "echo > secure_file.txt"). Am I missing something, or is the patch missing something?

David


(Log in to post comments)

Does this not handle unsafe overwrites?

Posted Dec 8, 2006 1:15 UTC (Fri) by nix (subscriber, #2304) [Link]

Yeah, I have a feeling this is yet *another* problem with this proposal.

I guess I should go and read the actual patch and moan on l-k if these
problems really do exist. (Still, I'm the last-ditch Viro Defence Force
would spot them if I didn't complain. I'm almost tempted not to moan
because Al's demolition is bound to be so much more amusing than any I
could come up with... ;) )

Does this not handle unsafe overwrites?

Posted Dec 8, 2006 19:03 UTC (Fri) by giraffedata (subscriber, #1954) [Link]

Right. What we want is secure de-allocation, not secure delete. That looks more like attaching deallocated blocks to a .trash file than linking unreferenced files to a .trash directory.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds