Submitted On 18-JUL-2003
ulibube
Here's a link to a forum discussion with additional information:
http://forum.java.sun.com/thread.jsp?
forum=60&thread=414869
Submitted On 28-NOV-2003
Pie-Fed
The state says closed-fixed, but I just downloaded 1.4.2_02
for w2k, and this bug still exists.
Submitted On 02-DEC-2003
Pie-Fed
Sorry, I didn't understand that "tiger" means 1.5
Submitted On 15-JAN-2004
gt
You guys have got to be kidding me. You don't plan on
fixing this in 1.4.2!?!?!? What's with that? How can you
*NOT* fix it for 1.4.2?
Submitted On 28-JAN-2004
mattsecoske
I agree. This needs to be fixed... I have customers that
are running up against this.
Submitted On 22-MAR-2004
jtwow
1.5 is not a stable product, 1.4.2_03 is a stable
product, yet this is marked closed? What about the
rest of us using the latest stable builds with real
customers out there?
Submitted On 26-MAR-2004
bgoetz
We are also forced to stay on jdk 1.3.1_x with a specific
component with our customers. The migration of the
keystore costs money so they reject it. Please fix this in
1.4.2!
Question: *IF* we get the customer to migrate the
keystore, do we need to remigrate for 1.5?
Submitted On 14-JUN-2004
mark@mindreef.com
Note: it does say fixed in 1.4.2_05, just not sure when that will be out...
Submitted On 14-JUL-2004
ewsachse
I downloaded the 1.4.2_05 JSDK, and it cannot read a keystore I created in 1.4.2_03.
Way to go Sun.
Submitted On 23-JUL-2004
rpisani
I have the same problem... keystore from 1.4.2_03 can't be read in 1.4.2_05... now what am I supposed to do!?!?
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|