> -----Original Message-----
> From: Douglas E. Engert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 15, 2007 8:27 AM
> To: Mattes, David
> Cc: Ludovic Rousseau; [email protected]
> Subject: Re: [opensc-devel] GemSafe driver
>
>
>
> Mattes, David wrote:
> >> -----Original Message-----
> >> From: Ludovic Rousseau [mailto:[EMAIL PROTECTED]
> >> Sent: Thursday, November 15, 2007 6:10 AM
> >> To: [email protected]
> >> Cc: Mattes, David
> >> Subject: Re: [opensc-devel] GemSafe driver
> >>
> >> 2007/11/13, Douglas E. Engert <[EMAIL PROTECTED]>:
> >>> 0x04, "01", SC_PKCS15_CO_FLAG_PRIVATE},
> >>>
> >>> Change the key reference for thr private key from 0x03 to
0x04.
> >>> This might be the difference in the cards or the way Gemsafe
> >>> formated them. Is there some other DF on the card that could
be
> >>> used to determine the key reference?
> >> David, do you have a regression with this change?
> >>
> >
> > I believe this would cause a regression. Here is the output of
> > pkcs15-tool:
> > X.509 Certificate [DS certificate]
> > Flags : 2
> > Authority: no
> > Path : 3f0016000004
> > ID : 45
> >
> > Private RSA Key [DS key]
> > Com. Flags : 1
> > Usage : [0x37], encrypt, decrypt, sign, wrap, unwrap
> > Access Flags: [0x1D], sensitive, alwaysSensitive,
neverExtract,
> > local
> > ModLength : 1024
> > Key ref : 3
>
> The 3 is what I changed to 4, to get it to work. But how do you know
> from the GemSAFE manuals, what key reference goes with what cert?
> Also why did you pick ID:45 for the cert and key?
>
I certainly did not find that information from the manual! Since I only
had 1 key and 1 cert, the mapping was obvious. And I did not provision
the card, so I did not pick those IDs. You have multiple certs and
keys?
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
