On May 14, 2010, at 11:36 , Jan Just Keijser wrote: >>> >> >> 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/
Sure. But you're talking about a different reader and a different card, which does not relate to the GemPC pinpad reader or the Entersafe driver at all. This is a limitation of the specific reader so it should apply universally to the reader, not to the card driver or the rest of OpenSC. -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
