Closed dirkx closed 8 years ago
Just one more point... I'd like to see this behavior documented. But I'm not quite sure where to put it.
On 26 Nov 2015, at 01:10, Frank Morgner notifications@github.com wrote:
Just one more point... I'd like to see this behavior documented. But I'm not quite sure where to put it.
Aye; there is no manpage; nor is there a SecTokendMain() its —help you could tie into. One could put it as a debug blob in the init; but that sounds ugly.
One could add an OpenSC man page (along with those for the various tools); so that a ‘man -k’ would pick it up; but that is just as arcane; as rarely anyone will put /Library/OpenSC/share/man or equivalent in their man path.
Dw.
I think extending README.md with known limitations would be a good idea
at all -and- we have a reader with its own PIN pad connected (e.g. a SPR532, ParityMedical, eH880, etc).
In that case; defer entry to the reader.
We do not, however, prevent the user from entering the PIN on the normal keyboard. As we're 'too late' already. If the user has already done that; we simply pass on the entered value.