From: <J.W...@mi...> - 2016-03-10 15:49:05
|
Hi all, Can anybody shine some light over this? We finally have found some pinpad-readers that do work under Linux, with our cards and the AET-drivers. For instance, if I type opensc-tool -l, I can see with readers have a pinpad or not Also, when I do pkcs11-tool -O -l, I _must_ enter the pin on the reader. Furthermore the screen-lock (driven by pam) knows when to ask for a pin, or refer to the reader-console. However, openvpn simply continueus to ask for the pin on the console (or its management interface). I presume openvpn should have checked the reader's capabilities, but forgot to do that... Secondly, as the code works with the pin on the prompt, I presume there is a switch (routine in libccid ??) that specifies IF a pinpad should be used or not? So you can optionally overrule the pinpad-capability??? Kind regards, Hans. ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. |