linux-ext4 - Re: [dm-devel] Some thoughts about providing data block checksumming 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]

Date:	Wed, 05 Nov 2014 22:37:09 +0100
From:	Milan Broz <gmazyland@...il.com>
To:	Mikulas Patocka <mpatocka@...hat.com>,
	Theodore Ts'o <tytso@....edu>
CC:	linux-ext4@...r.kernel.org, dm-devel@...hat.com
Subject: Re: [dm-devel] Some thoughts about providing data block checksumming
 for ext4

On 11/05/2014 01:27 AM, Mikulas Patocka wrote:

> So you really need cryptographic hashes instead of checksums to avoid the 
> collisions.

I am not sure if it was mentioned but also see how integrity is implemented in
FreeBSD GELI system by playing with sector sizes
 
http://svnweb.freebsd.org/base/head/sys/geom/eli/g_eli_integrity.c?view=co

Also, for encrypted devices (either on file level or block level) I think 
there are still requests for implementing real crypto authenticated modes (like GCM)
which obviously need similar space for auth tag. (I think ZFS uses it this way.) 

Milan

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