Date: Mon, 17 Aug 1998 14:44:26 -0700 (PDT)
From: Jan Luehe <luehe@laguna.eng.sun.com>
Subject: Re: javakey
To: java-security@java.Sun.COM, OrtmannV@lsv-gartenbau.de
Volker:
> javakey -gc cert_directive_Duke
>
> ... and always I got the messages:
>
> "Error parsing issuer.cert number." or "No such cert ... ".
>
> This example I followed step by step, comes from the sun homepage. These are
> the instructions, which I followed exactly :
>
>
>
> Steps for creating and signing a JAR file, short version
> Set up path
> % setenv PATH ~/java/bin:$PATH
> Create an identity.
> % javakey -cs "duke" true
> Generate DSA key pair for the identity.
> % javakey -gk "duke" DSA 512 duke_pub duke_priv
> Generate certificate
> Create a cert_directive file (See example, below)
> % javakey -gc cert_directive
> Create a jar file (syntax is like tar.)
> % jar cf demo.jar PhoneServlet.class
> Sign the jar file
> Create a sign_directive file (See example, below)
> % javakey -gs sign_directive demo.jar
> The signed jar file will be written to a file named "demo.jar.sig."
> Rename this file so that it has the suffix .jar, so that it can be read and
> unjar-ed by the applet classloader.
> By default, the jar tool doesn't overwrite your original jar file.
> % mv demo.jar.sig demo.jar
Can you make sure that "issuer.name" and "subject.name" (in your
cert directive file) are the same (this will cause a self-signed
cert to be created) and correspond to one of the
signer identifies in your identity database?
In your example, you should set both "issuer.name" and "subject.name"
to "duke".
This might help you get started.
Jan