On Fri, Sep 07, 2001 at 01:51:14AM -0500, Rob McGee wrote:
> While I'm here, and rather than write another post, I'd like to address
Ah, but silly me, I have one more question. Playing with it some more, I
applied the 2.4.6 patch to my kernel loop driver (2.4.9, but it applied
cleanly.) Then I recompiled the loop.o (it's a module) compiled the
cryptoapi-2.4.7.0 again, make install, depmod, modprobe cryptoloop (kmod
is enabled too.)
Now I can't access my encrypted loop file which was created under the
kerneli 2.4.3.1 patch. Is this to be expected?
Anyway, that's no worry, because I can easily switch back to the other
loop.o and cryptoapi modules, and I don't really need that loop file.
But I'm really not clear on what is the tradeoff in using
--enable-iv-mode-sector vs. not using it. If I gain universal access to
files on alternate media, that's great. What do I lose besides a little
backward compatibility? Or is that it?
Rob - /dev/rob0
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
