Martin Paljak wrote:
> On May 11, 2010, at 19:44 , Ludovic Rousseau wrote:
>
>> I think you will need this patch to use the Gemalto pinpad:
>>
>> Index: src/libopensc/card-entersafe.c
>> ===================================================================
>> --- src/libopensc/card-entersafe.c (revision 4340)
>> +++ src/libopensc/card-entersafe.c (working copy)
>> @@ -938,7 +938,7 @@
>> {
>> pin->encoding = SC_PIN_ENCODING_ASCII;
>> pin->min_length = 4;
>> - pin->max_length = 16;
>> + pin->max_length = 8;
>> pin->pad_length = 16;
>> pin->offset = 5 + num * 16;
>> pin->pad_char = 0x00;
>>
>> The reader does not accept PIN longer than 8. I willl write about that
>> on my blog [1] later.
>>
>
> In this case it should be either fixed in reader-pcsc.c for this reader (if
> it is possible to auto-discover it, which may not work on Windows for
> example) or forced to a reader-suitable value in the CCID driver.
>
> I guess 99% of people don't have longer than 6 or 8 digit PIN-s in real life
> (which also seems to be the way Gemalto things)
>
one of the reasons we are using Aladdin eTokens is because it allows a
PIN (password, really) that is 12 characters or longer. Thus I'd be
strongly against limiting the PIN to anything shorter than what the card
allows: we cannot foresee the security restrictions that the user has
when searching for a particular card/token/
cheers,
JJK
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
