Hi,
I implemented support (currently only RSA) Rutoken ECP tokens (in Russian http://rutoken.ru/products/rutokends/) for OpenSC.
Worked: ccid-1.3.10 + pcsc-lite-1.5.4 (pcsc-lite-1.5.2) + opensc
Patch for trunk revision 3695 is in attachment.

Initialize:
$ pkcs15-init --erase-card --create-pkcs15 --so-pin "87654321" --so-puk ""
$ pkcs15-init --store-pin --label "User PIN" --auth-id 02 --pin "12345678" --puk "" --so-pin "87654321" -F

Rutoken ECP:

T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0a89 ProdID=0030 Rev= 1.00
S:  Manufacturer=Aktiv
S:  Product=Rutoken ECP
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=0b(scard) Sub=00 Prot=00 Driver=usbfs
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

On-board cryptographic functions:
- RSA (with RSA keys up to 2048 bits)
- GOST R 34.10-2001
- GOST 34.11-94
- GOST 28147-89
- Key generation: ElGamal and Diffie-Hellman schemes
- Random number generator

Authentication:
- 3 categories of owners: Administrator, User, Guest
- 2 Global PIN-codes: Administrator and User
- Local PIN-codes
- Combined authentication
- The possibility of simultaneous control of the access rights by the 7
Local PIN-codes

File system features:
- File structure of ISO/IEC 7816-4
- The level of subdirectory - limited by space available for file system
- Number of file objects inside directory - up to 255, inclusive
- Using files Rutoken Special File (RSF-files) to store keys and PIN-codes
- Storage of private and symmetric keys, without the possibility of
exports from device
- Predefined directory for storing different kinds of key information
(RSF-files) and automatic selection of the predefined directories
- The total amount of memory for file structure - 64 kB

Could you add patch if possible?
Thanks

Attachment: opensc-trunk-r3695-rtecp.diff.gz
Description: application/gzip

_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to