# Re: jarsigner ambiguity

Jan Luehe (luehe@laguna.eng.sun.com)
Tue, 5 Jan 1999 11:49:59 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jan Luehe: "Re: Add SunJCE provider with JDK1.2"
- Previous message: Jan Luehe: "Re: jce licensing fees?"
- Maybe in reply to: =?iso-8859-1?Q?J=E9r=F4me?= Beau: "jarsigner ambiguity"

Jerome:

> I did not found any documentation about the verification results of the
> jarsigner tool. I can see the "smk" flag near my class file in these
> results, and not the "i" flag. I understand "found in keystore", but
> what do you mean by "found in the identity scope" ?

This is for backwards compatibility with signer identities
imported into identity scopes created using "javakey" in JDK
releases prior to JDK 1.2.

The "i" flag indicates that the class which it precedes was signed
with a private key whose corresponding public key was found in the
caller's identity database.

Note that in JDK 1.2 we replaced "javakey" with "keytool", and
"identity database" with "keystore", and added a "keytool" command
option that allows you to convert
an existing identity database (created prior to JDK 1.2) to a
corresponding keystore.

Jan

- Next message: Jan Luehe: "Re: Add SunJCE provider with JDK1.2"
- Previous message: Jan Luehe: "Re: jce licensing fees?"
- Maybe in reply to: =?iso-8859-1?Q?J=E9r=F4me?= Beau: "jarsigner ambiguity"