[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [iaik-ssl] DES(3) and IV



iSaSiLk 3.02 and later never call doFinal() on a cipher, so it is irrelevant
what implementations do when doFinal() is called. Hence, there are no
interoperability problems with other crypto providers. And as iSaSiLk
interoperates with the Microsoft, Netscape, OpenSSL, ... SSL/TLS
implementations there are obviously no problems in this respect either.

 Andreas Sterbenz              mailto:Andreas.Sterbenz@iaik.at


----- Original Message -----
From: "Schlueter, Michael" <Schlueter@secunet.de>
To: <iaik-ssl@iaik.at>
Sent: Friday, January 19, 2001 2:48 PM
Subject: [iaik-ssl] DES(3) and IV


I found the following thread in the iaik-jce mailinglist archive. In my
opinion this issue is a big problem for the current iaik-ssl implementation.

The iaik-jce provider does not reset the IV after the doFinal call for a
CBC-Cipher object. So if the same Cipher object is used twice without
calling Cipher.init in between, the second operation does not use the
initial IV.
This behavior is different in other implementations like Sun and Aba.
The current isasilk implementation uses the read_cipher and write_cipher
object in the handshaker twice without calling Cipher.init in between. So if
a SSL server based on isasilk uses the iaik-jce provider and the client uses
a different jce provider, the handshake will fail, since the decryption will
give different results.
What about the compatibility between isasilk based ssl implementations and
other products?

Any suggestions?
Michael Schlüter



smime.p7s