--=_courier-30829-1056116453-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Andrew Morton wrote:
> Fruhwirth Clemens <clemens-dated-1056963973.bf26@endorphin.org> wrote:
>>
>> If this bug is fixed, we can go ahead and add cryptoloop which is ready
>> and tested.
>
> Does it use the crypto framework which is present in the 2.5 kernel?
Yes.
> If it does not then the cryptoloop implementation which you mention
> is inappropriate for inclusion.
>=20
> If it does then it would be nice to see the full patchset.
http://therapy.endorphin.org/patches/cryptoloop-0.2-2.5.58.diff
It's basically a stub. The lock of the cipher_context can be removed since
post-2.5.58 a new call has been added which makes the IV an argument.
However, that's a minor change.
In case you want to test it, you need to patch losetup too, since it needs
to parse /proc/crypto.=20
http://therapy.endorphin.org/patches/losetup-2.5.diff
Regards, Clemens
p.s.: Andrew please send me carbon copies of your mails. Thanks.
--=_courier-30829-1056116453-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+8w5IW7sr9DEJLk4RAq4QAJ0SrcZLBAHCVAwQ6Lnx5Ljfvb+dCACeKBvf
L1UULrdY1foYO+9LcvqFZ/Y=
=asJ+
-----END PGP SIGNATURE-----
--=_courier-30829-1056116453-0001-2--