On Tue, 2006-08-01 at 15:38 +0200, Paul Santapau Nebot wrote:
>> I'm trying to guess how the CKA_ID is calculated from the public key
>> when nss generates a rsa key pair and try to store in a smart card
>> via pkcs11 (C_CreateObject) assigning an ID (CKA_ID).
>> Somewhere in the documentat
On Tue, 2006-08-01 at 15:38 +0200, Paul Santapau Nebot wrote:
> Hello,
>
> I'm trying to guess how the CKA_ID is calculated from the public key
> when nss generates a rsa key pair and try to store in a smart card
> via pkcs11 (C_CreateObject) assigning an ID (CKA_ID).
> Somewhere in the doc
On Mon, 2006-07-31 at 21:52 -0500, Rich Raffenetti wrote:
> e certificates are auto enrolled and are replaced every month. We
> don't
> wish for our 3500 users (even 10% of them) to have to export and
> import the
> certificates for Firefox. Moreover, the certificates are marked
> non-exportab
Paul Santapau Nebot wrote:
Somewhere in the documentation [1] is said that CKA_ID is
generated from some part of the public key but it is not specified
which part.
That documentation is incomplete. I found more info here, but I don't
know where you should find the latest version of that :
Hello,
I'm trying to guess how the CKA_ID is calculated from the public key
when nss generates a rsa key pair and try to store in a smart card
via pkcs11 (C_CreateObject) assigning an ID (CKA_ID).
Somewhere in the documentation [1] is said that CKA_ID is
generated from some part of the p
5 matches
Mail list logo