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 for Android: free password hash cracker in your pocket

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

Message-Id: <2006-10-31-14-02-00+trackit+sam@rfc1149.net>
Date:	Tue, 31 Oct 2006 14:02:00 +0100
From:	Samuel Tardieu <sam@...1149.net>
To:	Erik Mouw <erik@...ddisk-recovery.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Shred mount option for ext4?

On 31/10, Erik Mouw wrote:

| Why don't you just make a libc wrapper for the unlink(2) system call?
| (A modified libc.so should do as well). That way it will work for all
| of your applications on all filesystems.

Because this won't take care of the journal, which may contain an extra
copy of the previously written data. Also in transactional filesystems,
overwriting data doesn't guarantee that the data is written in the same
place: it will typically be written at another place and then the
metadata will be updated afterwards. You have no control about that at
user level, since you can't hook into the block freeing routine.

Thanks for the reference btw :)

-
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