Re: [CryptoAPI-devel] dfc / util-linux rpms

[Ben S. <sl...@st...>]

Hm..
Looking at the SRPM, it seems that you've added SHA1 password hashing
into the old util-linux-cryptoapi patch. Now it occurs to me: maybe
instead of tacking hash algorithms onto util-linux, we might be better
off sending the unhashed password into kernelspace, and let cryptoloop
do the hashing itself.

I can think of arguments for and against this. OOH, it seems like a
bad idea to make the kernel do what can be (and is) done just fine in
userspace. OTOH, we already have the digest algorithms in the kernel;
it seems like a waste to recode them, especially in a _separate_ patch,
and especially when the result is immediately handed off to cryptoloop.

Thoughts? Flames?

-- 
Ben Slusky                      | It is amazing how many eggs
sl...@st...              | one can break without making a
sl...@pa...          | decent omelette. 
PGP keyID ADA44B3B              |       -Charles P. Issawi