![]() | |||||||||||||
Messages in this thread |
Hi! > > > Well, CTR mode is not recommended for encrypted file systems because it is very > > > easy to corrupt single bits, bytes, blocks, etc without an integrity check. > > > If we add a MAC, then any mode of operation except ECB can be used for > > > encrypted file systems. > > > > what does "easy to corrupt" mean? i haven't really seen disks generate > > bit errors ever. this MAC means you'll need to write integrity data for > > every real write. that really doesn't seem worth it... > > The difference between "_1,000,000" and "_8,000,000" is 1 bit. If an > attacker knew enough about the layout of the filesystem (modify times on blocks, > etc) they could flip a single bit and change your _1Mil purchase order > approved by your boss to a _8Mil order. Hmm... long time ago I created crc loop device to catch faulty disks. If cryptoloop can do that for me... very good! -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | |||||||||||||