Andreas Jellinghaus wrote: > Am Mittwoch 28 Januar 2009 19:30:52 schrieb Stanislav Brabec: > > How to name the main category "smart_card_reader or crypto_token"? > > I think it is easer to explain, that a usb crypto token is a device consisting > of a reduced smart card reader and a fixed build in smart card. I guess > this is quite close to the truth. the other way would be more like the pkcs#11 > document (they talk about tokens all the time, but cover software > implementations too), and harder to explain I think.
OK. Considering consensus on "info.category: smart_card_reader", I will appropriately correct the patch in http://bugs.freedesktop.org/show_bug.cgi?id=19663 Nothing more is actually needed for PolicyKit. > > 2) Use "smart_card_reader" and invent a different name for "the one with > > slot for cards". > > maybe something like "slots:1" , "slots:2", "slots:fixed"? smart_card_reader.num_stots. But I guess that we can live without this key, as separate key would be more flexible. To discriminate between these two types of devices, capabilities line "smart_token" and "smart_card_slots" would be sufficient. > or use the card size format here? (e.g. "slots:id0,wireless" ?) > not 100% sure No. It is not scalable. Once in future, your would want to assign another key to slot, and it would be impossible (or it would introduce ugly parsing problems). It would be better to postpone these keys to possible future separate HAL record for slot. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: [email protected] 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 [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
