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
Ok, I agree since nobody seems to complain .
So I will try this in the nest release
Thanks,
François.
Martin Paljak a écrit :
> Hi.
>
> Correct, this is a bug. I've never used GLP PINs and apparently no one
> else tried them either until now.
>
> Fixed in [3664]
>
> Thanks,
> Martin
>
> On 1
Hi.
Correct, this is a bug. I've never used GLP PINs and apparently no one
else tried them either until now.
Fixed in [3664]
Thanks,
Martin
On 11.03.2009, at 20:45, Alon Bar-Lev wrote:
> Great work!
> Can someone confirm current hardware still works?
> I never had PINPAD reader to play with.
