Date: Thu, 31 Jul 2003 05:45:27 +0200
From: Frank v Waveren <fvw@var.cx>
To: linux-kernel@vger.kernel.org
Cc: Andries.Brouwer@cwi.nl, linux-crypto@nl.linux.org
Subject: 2.6.0-test2+Util-linux/cryptoapi
Message-ID: <1059621603HIC.fvw@tracks.var.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1507
Lines: 31

I was giving 2.6.0-test2 a spin, and run into a few issues with
loopback crypto:

First of all, in util-linux 2.12 the keybits option is gone, and the
number of keybits is fixed to 256 (even though some algorithms in the
kernel support more). Is this a temporary thing or a design decision?

Moving to the slightly more ontopic stuff for lk@vger: Is access to
the cryptoapi algorithms exposed to userspace yet? I wanted to have
losetup/mount hash the passphrase before passing it to the kernel, and
it seems silly to actually put a separate hashing algorithm in
util-linux when they're there in the kernel anyway.

Thirdly, has the encryption setup changed again since 2.4.x with hvr's
testing cryptoapi stuff? I have a filesystem encrypted with 256 bits
serpent, yet it won't decrypt using 2.6.0-test2 and util-linux 2.12.

Lastly: Why the move from a /proc/crypto directory containing files
for all the algorithms to one monolithic /proc/crypto file? Isn't the
former a lot nicer from the userspace programmer's point of view?


-- 
Frank v Waveren                                      Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100            1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx            7BD9 09C0 3AC1 6DF2
-
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/