Hello Martin, > -----Original Message----- > From: Martin Paljak [mailto:martin.pal...@gmail.com] On Behalf Of Martin Paljak > > Hello, > On Apr 28, 2011, at 11:37 , Toni Sjoblom - Aventra wrote: > > Don't know how this could be done for OpenSC, since it caches PIN codes. > Only if the PIN does not cache "user consent" keys and only if PIN caching is > enabled.
Ok, well then everything is set, just didn't know about this :) > > > This is something called "User Consent", and is a common standardized > > feature. MyEID supports this but I dont know if OpenSC does. > > The OpenSC PIN cache should take this into account when caching PINs and > > somehow it should be possible to create PINs or keys that have this flag > > set. > > Yes it does support using such PIN-s. OpenSC does not cache the PIN if any > private key with user consent has the PIN as authentication ID. Creating them > is AFAIK not possible through command line (a feature request ticket might be > good) Nice! I'm sure there are a lot of features people (including me) don't know about. I will create a feature request (add a command line switch for user-consent). Have a nice day, Toni _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
