Javakey DOA on JDK 1.1.7/Win 95

Didier Frick (dfrick@dial.eunet.ch)
Sun, 18 Oct 1998 00:11:11 +0200

Message en plusieurs parties et au format MIME.

------=_NextPart_000_0004_01BDFA2B.CFC25880
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It looks like javakey is completely messed up in JDK1.1.7 / Win 95

I have aready submitted a bug about javakey -gk crashing the JVM, but in =
addition to that I notice that all nontrivial functions (which involved =
some cryptographic algorithm) seem broken: -gc and -gs just lock up the =
machine.

I have already tested and used javakey successfully on the very same =
system running JDK1.1.5, so I'm pretty convinced there's something =
awfully wrong in this version of Javakey at least under Windows.

Furthermore, I have noticed incompatibilities with previous versions =
(issuer organization is now required to generate a certificate, which =
was not the case until now), which are absolutely not documented in the =
release notes.

Didier

------=_NextPart_000_0004_01BDFA2B.CFC25880
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

It looks like javakey is completely = messed up in=20 JDK1.1.7 / Win 95
 
I have aready submitted a bug about = javakey -gk=20 crashing the JVM, but in addition to that I notice that all nontrivial = functions=20 (which involved some cryptographic algorithm) seem broken: -gc and -gs = just lock=20 up the machine.
 
I have already tested and used = javakey=20 successfully on the very same system running JDK1.1.5, so I'm pretty = convinced=20 there's something awfully wrong in this version of Javakey at least = under=20 Windows.
 
Furthermore, I have noticed = incompatibilities=20 with previous versions (issuer organization is now required to generate = a=20 certificate, which was not the case until now), which are absolutely not = documented in the release notes.
 
          &nbs= p;            = ;        =20 Didier
 
------=_NextPart_000_0004_01BDFA2B.CFC25880--