Alternate smartcardio provider

Michael Traut michael.traut at gmail.com
Thu Jul 18 23:48:13 PDT 2013


As suggested by "helpcrypto", this is a cross post from muscle mailing
list... If someone is interested...

Our initial release for a PC/SC binding and an alternate javax.smartcardio
provider is now included in https://github.com/intarsys/smartcard-io/.

For the smartcardio implementation itself we have the following state:

* Intended differences
** dedicated PCSC context for terminals, terminal and card (true
concurrency)
** waitForChange(timeout) semantics improved(?), state change is reset even
in case of timeout
** reader insertion is handled, too
** no finalizer for card!

* Open design questions
** "exclusive" card access is NOT restricted to a Java thread. We found no
technical reason for this constraint. imho this makes handling of shared
and pooled resources ugly. Next to "Only one PSCS context" this would be my
top level reason *not* to use smartcardio. Any opinions?
** "connect" always returns the identical {@link Card} object. This is why?
This implementation currently opens a new shared connection. If we revert
to the spec, i'd at least expect some kind of reference counting. Opinions?

* Todos
** no channel support yet
** implement "GET RESPONSE"
** no permission checks so far
** review exceptions to be standard compliant (IllegalStateException)

We'd be happy if someone around wants to use and verify the lib in their
own project (as we do not rely on smartcardio...)

Regards, Michael Traut
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20130719/50af9fae/attachment.html 


More information about the distro-pkg-dev mailing list