Re: [CryptoAPI-devel] testing...

[David B. <db...@du...>]

So kyle and I breifly spoke about the IDEA algorithm being in the API.=20
Since it is still patented(until 2007 IIRC) we felt it shouldn't be in
there and should be available seperately as a patch.  Thoughts on this ?
I haven't had a chance to pour over the sources for a few hours, and get
to know them, but I plan to soon.  I'm also looking into how cfs was
designed for OpenBSD because it would be nice if linux could eloquently
support encrypted root/swap.
cheers,
dave

On Sun, 2002-02-24 at 17:02, Herbert Valerio Riedel wrote:
> On Sun, 2002-02-24 at 19:22, Kyle McMartin wrote:
> > one two three.
> works!
>=20
> well, I'll take the opportunity write about the current status;
>=20
> ...we are quite alone here, just 3 of us in the mailing list so far...
> hope we become more over time :)
>=20
> ok, so we have=20
>=20
> 1. a 'cryptoapi-2.4.7' tarball which is a bit out of date at
> sourceforge.net
> 2. a CVS repository containing the latest cryptoapi code at sourceforge
> 3. the old kernel patches up to 2.4.3 at kernel.org (by alex)
> 4. the 'testing' patches up to 2.4.17 at kernel.org (by me), containing
> code from the cryptoapi-branch...
>=20
> some unresolved problem which kept me from releasing this beast finally
> are:
>=20
> 1. how to automate the task of creating a kernel patch from the
> cryptoapi-CVS? or maybe just do it like the frees/wan people do?
> 2. how to handle jari's and my loop-IV fix approach in a compatible way.
> 3. documentation update
> 4. some stuff I forgot... :-/
>=20
> ..if something is unclear (and I'm sure there is :-), please don't
> hesitate to ask! :-)
>=20
> regards,
> --=20
> Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
> Email: hv...@hv...       /    Finger hv...@gn... for GnuPG Public Key
> GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
> 4142