2010/5/18 Martin Paljak <[email protected]>:
> On May 18, 2010, at 10:30 , Ludovic Rousseau wrote:
>> 2010/5/14 Martin Paljak <[email protected]>:
>>> On May 11, 2010, at 19:44 , Ludovic Rousseau wrote:
>>>> 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.
>>
>> It is possible to fix the code. I discuss the problem in [1].
>> The solution is to use a new possibility of PCSCv2 part 10:
>> FEATURE_GET_TLV_PROPERTIES
>>
>> I may try to work on a patch for OpenSC but I don't know when.
> From your blog post:
>
> "Since PCSCv2 part 10 v2.02.07 from March 2010"  and "Do not expect any thing 
> from Microsoft. Their CCID driver and PCSC middleware are frozen in ice since 
> some time (in years)."
>
> I thud don't believe it will be universally available, even with vendor 
> drivers on Windows (what IMHO is the default, as Windows update usually wants 
> to download the vendor drivers if you have the reader plugged) any time soon.

You are right. It will not work universally before a long time.

My idea is to make it work at least for _me_.

>>> 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)
>>
>> I also think so.
> What about reseting the size limits to what the reader supports in the driver?

That is another option. But I think it is too intrusive.

> What does the Windows driver do with PIN sizes that do not fit into the 
> supported range?

I don't know what the Windows driver does.

> I think limiting the lower limit to 4 digits would be a good idea for OpenSC 
> as well...

It is already the case (at least for src/libopensc/card-entersafe.c)

Bye

-- 
 Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to