| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <bug-92271-13602-rS2dmH3FhI@https.bugzilla.kernel.org/> Date: Sun, 01 Feb 2015 10:14:39 +0000 From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 92271] Provide a way to really delete files, please https://bugzilla.kernel.org/show_bug.cgi?id=92271 --- Comment #14 from Alexander Holler <holler@...oftware.de> --- The FS doesn't have to give a promise for the storage. If the storage doesn't overwrite the same blocks (which it did for 25 years and still does on most conventional HDs) and doesn't offer a way to really get rid of stuff (like Secure Trim), then the storage can be blamed. Using encryption is just a workaround. And what makes you believe that the used encryption is secure? Or that the used encryption is still secure in some years. Encryption often suffers under bugs in the implementation, bugs in the algorithm itself and from Moore. Just think at all the "encrypted" zip-archives. I a few years people might laught about the stuff used today to encrypt. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists