(joining two sub-threads)
Andreas Jellinghaus wrote:
> new topic: usb crypto tokens
> I think we should have both "smart_card_reader" and "usb_crypto_token"
> for those token with internal smart cards (e.g. aladdin etoken pro and
> friends). it could confuse the users if we say they are smart card readers.
Ludovic Rousseau wrote:
>Could "usb_crypto_token" be a subclass of "smart_card_reader" or
>something similar?
I have been thinking about it as well.
Regarding smart tokens, the "smart_card_reader" is confusing.
Returning back, iso7816 may be really better:
category: iso7816.smart_card_reader
category: iso7816.smart_token
Or maybe better:
Category: iso7816
Capabilities: smart_card_reader or smart_token
I'll consult it with HAL developers and ask, what they would suggest.
>The information you should report are what you can do with the reader,
>not how it works.
>So it may be:
>- manufacturer name
>- product name
Done automatically by USB inquiry, but it's possible to overwrite.
>- class 1
>- class 2 : pinpad
>- class 3 : pinpad + display
>- number of slots ?
Agree.
It opens an implementation question:
Capabilities is a string.
That is why we may want dedicated keys:
iso7816.smart_card_reader.numslots = (int) (only reades may have more slots,
isn't it?)
iso7816.class = (int) {even tokens may have pinpad)
>But not:
>- ccid : this is of no use to the application
If we know that without any research, why not provide it.
>- openct : idem
As I wrote in another mail, it a recommended way of assigning to driver.
However it should not be a part of cababilities.
>You could reports all the fields of the USB CCID descriptor. See [2]
>for an example. But that may be too much and non-CCID reader do not
>report all these values.
I guess we can start with a small number of entries.
We will find, whether it is useful and well defined. Later it should be
possible to extend information in a compatible way.
Several notes are in Bugzilla about it:
http://bugs.freedesktop.org/show_bug.cgi?id=19663
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbra...@suse.cz
Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
