Message-Id: <01BC5BB0.89F1D3F0@impetus.ctron.com>
From: Jon Willard <willard@ctron.com>
To: "'java-security@web2.javasoft.com'" <java-security@web2.javasoft.com>
Subject: FW: Question on javakey and java.security
Date: Thu, 8 May 1997 13:05:43 -0400
Ok ... I spoke too soon ... it appeared to have worked once then started =
failing again. I will continue to investigate. All ideas are welcome.
Jon (having quite a discussion all by myself)!
----------
From: Jon Willard[SMTP:willard@ctron.com]
Sent: Thursday, May 08, 1997 12:52 PM
To: 'java-security@web2.javasoft.com'
Subject: FW: Question on javakey and java.security
I believe I found my problem(s):
1. Apparently the key must be encoded before being written to a file if =
Javakey is going to understand it. It was educational to view the =
serialized key vs. The encoded key in a binary editor.
2. Apparently the identity must be a signer. This makes sense now.
Thanks,
Jon
----------
From: Jon Willard[SMTP:willard@ctron.com]
Sent: Thursday, May 08, 1997 11:56 AM
To: java-security@web2.javasoft.com
Subject: Question on javakey and java.security
I build a DSA x5.09 512 bit key using generateKeyPair() in jdk1.1.1. I =
then ship the public key over the wire as a Serialized Object ( =
objectoutputstream.writeobject()). The other side of the wire does an =
object read, and the an objectwrite to a file. The file should now =
contain an X.509 DSA public key which I can use in javakey -ik <file>.
However I get the following error:
C:\java\SecureFiles> javakey -ik willard c:/tmp/willard
Error: io error[DerInput.getLength(), unsupported [ 109 ]]
and my identity db does indeed contain willard
What gives?
Jon