[lkml]   [2000]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: A patch to loop.c for better cryption support
> On Fri, Oct 13, 2000 at 04:19:49AM +0000, Ingo Rohloff wrote:
> 2.4 has already broken backwards compatibility to 2.2 (IV changed
> from disk absolute to relative). When you change it now (before 2.4.0)
> it is relatively painless. I think the change is a good idea.

I've been away from the list for a while, so this has probably been
But, it seems to me that being able to have a different IV for
each filesystem would be a good thing, but having it depend on something
as volatile as sector of the disk, seems bad.
What about the first block of the underlying file holding an IV?

Then, if a loopback mount attempt finds a valid IV block at the
start (heavily CRC'd or similar, so the likelyhood of it ever
finding false magic is negligable (Say 10^-50)) it mounts
the filesystem, using the IV found.

Please tell me where the glaring error is :)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:3.133 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site