are routed through sc_pin_cmd(), which builds the APDU and either passes
it to the card directly, or to the card reader along with a request to
read the PIN(s) from the reader's keypad.
Currently, entering PIN in the standard way (i.e. via the application)
should still work - I have verified GPK and eToken; Cryptoflex verify
should work as well. Anything else needs additional testing, and support
for keypad input in particular (I cannot test this at the moment for
lack of a suitable reader).
git-svn-id: https://www.opensc-project.org/svnp/opensc/trunk@811 c6295689-39f2-0310-b995-f0e70906c6a9
eliminates duplicate code, and that we also pick up the new ATR if another
card was inserted in the meanwhil.
git-svn-id: https://www.opensc-project.org/svnp/opensc/trunk@758 c6295689-39f2-0310-b995-f0e70906c6a9
- Changed call convention for reader finish()
- CT-API driver now frees its resources correctly
- Added year 2002 to some of the copyright statements
- sc_pkcs15_decipher() and sc_pkcs15_compute_signature()
now select only the parent DF of the private key file
git-svn-id: https://www.opensc-project.org/svnp/opensc/trunk@463 c6295689-39f2-0310-b995-f0e70906c6a9
add support for e.g. CT-API
- renamed ops_data field to drv_data in struct sc_card
- copied coding style document from Linux kernel
git-svn-id: https://www.opensc-project.org/svnp/opensc/trunk@221 c6295689-39f2-0310-b995-f0e70906c6a9
okir
aet
fabled
jey