| 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-cjVAYPo1yK@https.bugzilla.kernel.org/> Date: Sun, 01 Feb 2015 17:18:46 +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 #18 from Alexander Holler <holler@...oftware.de> --- And if the encrypted content isn't really deleted, what happens if the key has gone away before it was "flushed" (whatever that means)? Which doesn't sound that unlikely after we've learned about the resources governments are using to get their hands on such stuff. So one could say one problem was exchanged against another, if the storage isn't really erased (which leads to original problem). Anyway, maybe the easy way I've used to fix fat in a few hours works for extN too. No idea if and when I will try or even post patches, as I personally don't have any problem with all that and are happily able to secure my own stuff according to most of my needs (hopefully). So I'll now stop arguing (likely to your pleasure) ;) -- 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