Weitao Sun wrote:
> Martin Paljak wrote:
>
>> On 18.03.2009, at 5:00, Weitao Sun wrote:
>>
>>
>>> 4.The user want a second keypair(KEYPAIR_B), so we will alloc a new ID
>>> for it. We, again, start from DEFAULT_ID(0x45) to 0xFF, pick a number,
>>> because KEYPAIR_A's ID is not DEFAULT_ID(0x
Martin Paljak wrote:
>
> On 18.03.2009, at 5:00, Weitao Sun wrote:
>
>> 4.The user want a second keypair(KEYPAIR_B), so we will alloc a new ID
>> for it. We, again, start from DEFAULT_ID(0x45) to 0xFF, pick a number,
>> because KEYPAIR_A's ID is not DEFAULT_ID(0x45), we pick 0x45 again.
> Quickfix
On 18.03.2009, at 5:00, Weitao Sun wrote:
> 4.The user want a second keypair(KEYPAIR_B), so we will alloc a new ID
> for it. We, again, start from DEFAULT_ID(0x45) to 0xFF, pick a number,
> because KEYPAIR_A's ID is not DEFAULT_ID(0x45), we pick 0x45 again.
Quickfix could be to assign the ID like
Hello,
Weitao Sun wrote:
> The plicy we alloc new ID is, picking a number in range from
> DEFAULT_ID(0x45) to 0xFF, if there is no object using it.
> Thus the ID is 0x45 because the key is the first object. We
> determine the path of the public key using object ID and template
> defined in card's
Hi list,
I have met with a problem when enroll more than one certificates using
firefox(3.0.7). I traced the process, and found what happend.
Here is the steps:
1.sc_pkcs15init_generate_key was called to generate a keypair, let us
name it KEYPAIR_A. Firefox didn't give it CKA_ID attribute, so
