Re: csp/pkcs11 container name management
From: Jakub Gwozdz (gwozdziu_at_rpg.pl)
Date: 10/06/05
- Previous message: Jakub Gwozdz: "Re: csp/pkcs11 container name management"
- Maybe in reply to: Dejan: "csp/pkcs11 container name management"
- Next in thread: Dejan: "Re: csp/pkcs11 container name management"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 6 Oct 2005 18:50:26 +0200
Dnia Thu, 6 Oct 2005 09:13:02 -0700, lelteto napisał(a):
> Since CKA_ID and CKA_LABEL is frequently used for other purposes (eg. CKA_ID
> is traditionally the hash of the modulus) it's better to use VENDOR_DEFINED
> CKA values (ie. >= 0x80000000) eg #define CKA_CONTAINER_NAME 0x80001110. Than
> you can store the container name to EACH Cryptoki object you plan to keep in
> that container. To distinguish between AT_SIGNATURE and AT_KEYEXCHANGE
> keypairs you can also add another vendor-defined attribute.
But CKA_VENDOR_DEFINED is VENDOR defined, not USER defined, so if you
aren't also pkcs11.dll developer, It will be no use to you.
-- Jakub Gwóźdź gwozdziu@rpg.pl
- Previous message: Jakub Gwozdz: "Re: csp/pkcs11 container name management"
- Maybe in reply to: Dejan: "csp/pkcs11 container name management"
- Next in thread: Dejan: "Re: csp/pkcs11 container name management"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
