Re: announce; monolithic versions of the cryptoapi branch!

[Herbert Valerio Riedel <hvr@hvrlab.org>]

1.) I hope you also fixed some minor rejects you may have gotten in the
    top-level Makefile (that's a nasty difference between the -XFS branch
    and the plain linux kernel) otherwise the crypto/crypto.o might not
    get linked into the kernel image, and then you won't see any message
    regarding crypto initialization in dmesg(8)

    for non-XFS kernels I provided the patch against 2.4.8 which may apply
    to 2.4.9 and later as well... guess I'll have to re-diff against some
    newer kernel in order to avoid confusion... ;-)

2.) you need to patch your util-linux-2.11i with the patch contained in
    the same directory, where you got the crypto patch from... maybe one
    should make ready to use rpms of the patched util-linux stuff... even
    if IMHO you shouldn't trust binaries you didn't compile yourself.....

On Wed, 5 Sep 2001, Harmon Seaver wrote:

>     Okay, I took a virgin 2.4.9 source tree and applied the 2.4.10pre4
> patch to it. Then I applied the cryptoapi-2.4.10-pre4-xfs.diff patch to
> that, and, after configuring (this time will all the crypto stuff in the
> kernel rather than modules, and "yes" to all of them except DES), and
> compiled, booted -- seems to work okay, except I find no mention of
> crypto in /var/log/messages from the boot like there was before.  I also
> installed util-linux-2.11i.
>       Anyway, so, since obviously we don't have to modprobe cryptoloop,
> I just try  "losetup -e blowfish (or twofish, or aes, or whatever)
> /dev/loop0 /my file". For each of them, I get a "Unsupported encryption
> type blowfish " or whatever I try to use.  Hmm. Doing a man losetup, I
> see it still only lists the same 3 crappy old dinosaurs, so, what the
> heck -- I try des, even tho I didn't even put that in as a module. That
> gets accepted, then it asks for my password and I give it one, then it
> says "Init (up to 16 hex digits):" and I'm not sure what to put in
> there. What is this?
>     But obviously something is not working -- why is des accepted and
> nothing else? The FAQ says that I need a new losetup, but I've got the
> latest one. To be sure, I go to RedHat and download their latest losetup
> rpm which is 2.11b and install that -- same thing.

-- 
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hvr@hvrlab.org       /    Finger hvr@gnu.org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F 4142


Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/