linux-ext4 - RE: Shred mount option for ext4?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8C7C41A176AC0B468BEFB2EFD9BDAB9902426639@XCH-NW-5V2.nw.nos.boeing.com>
Date:	Wed, 1 Nov 2006 08:57:37 -0800
From:	"Wolber, Richard C" <richard.c.wolber@...ing.com>
To:	"Andreas Dilger" <adilger@...sterfs.com>,
	"Nikolai Joukov" <kolya@...sunysb.edu>
Cc:	"Erik Mouw" <erik@...ddisk-recovery.com>,
	"Samuel Tardieu" <sam@...1149.net>, <linux-ext4@...r.kernel.org>
Subject: RE: Shred mount option for ext4?

> On Wednesday, November 01, 2006 8:17 AM Andreas Dilger Wrote:
> 
> Did anyone discuss doing this with crypto instead of actually 
> overwriting the whole file?  It would be pretty easy to store 
> a per-file crypto key in each inode as an EA, then to 
> "delete" the file all that would be needed would be to erase 
> the key in a secure matter (which is a great deal easier 
> because inodes don't move around on disk).

If it's cheap to delete the keys, it's also cheap to harvest 
the keys. A per file crypto-key lowers the barrier to entry.

This is Schneier 101.


..Chuck..
-
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