[CryptoAPI-devel] Re: RFC ...

[Herbert V. R. <hv...@hv...>]

On Sat, 2002-03-02 at 02:40, Mark Cooke wrote:
> Thanks for the draft - I've just pulled it home to read.
btw, it's not polished up yet - it's WIP; I hope it the packaging is
self-explaining...
=20
> A few more datapoints on cipe + cryptoapi:
=20
> I upgraded Machine A to the 2.4.18-ac1 + crypto + cipe + iv-diff.
>=20
> Tried aes-cbc, dummy-cbc and the default internal cipe-blowfish, and
> all fail with a 'cipc0: decrypt CRC error'. (Machine A and B are both
> x86, so it shouldn't be endian-things)
>=20
> I've looked quite hard at the _encode and _decode calls but everything=20
> seems to match up in terms of moving around points to account for IVs=20
> being prepended.

btw the changes I did, were mainly to revert to the old API as of
patch-int-2.4.3, so that the weird version-dependent patch (which is
doomed to break, once cryptapi gets version indepent) I saw for CIPE
should become unecessary...=20

applications which need to re-entrantly encrypt data w/ the same cipher
context should use the new _iv variants (which correspond to the crypto
patches > 2.4.3  and <=3D 2.4.18.0) which pass the iv as arg pointer

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