Il 23/05/2012 15:12, Joemar Mante ha scritto:

>> Someone already tested that token? It's the only one I could find that
>> handles RSA4096...
>> http://www.acs.com.hk/index.php?pid=product&prod_sections=0&id=CRYPTOMATE64
Finally arrived -- shipment got "lost" and took quite a lot :(

> I have worked with ACS before handling products related to ACOS5/ACOS5 64K.
> Though we have not any test with open-sc using this particular card. Are
> you using it via a PKCS#11 middleware?
Trying to use opensc and openssl to handle it.

All I could obtain from it is:

[root@jago media]# pcscd -afd
00000000 debuglog.c:265:DebugLogSetLevel() debug level=debug
00000114 configfile.l:245:DBGetReaderListDir() Parsing conf directory:
/etc/reader.conf.d
00000025 configfile.l:287:DBGetReaderList() Parsing conf file:
/etc/reader.conf.d/GemPCTwin-serial.conf
00000046 pcscdaemon.c:518:main() pcsc-lite 1.8.2 daemon ready.
00002208 hotplug_libusb.c:421:HPEstablishUSBNotifications() Driver
ifd-ccid.bundle does not support IFD_GENERATE_HOTPLUG. Using active
polling instead.
00000058 hotplug_libusb.c:430:HPEstablishUSBNotifications() Polling
forced every 1 second(s)

(now I plug it in)
[1635886.755035] usb 6-1: new full speed USB device number 14 using uhci_hcd
[1635886.919253] usb 6-1: New USB device found, idVendor=072f,
idProduct=90db
[1635886.919258] usb 6-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[1635886.919261] usb 6-1: Product: CryptoMate64
[1635886.919264] usb 6-1: Manufacturer: ACS

(nothing gets printed by pcscd)

[ndk@jago ~]$ pkcs11-tool --module /usr/lib/opensc-pkcs11.so -L
Available slots:
Slot 0 (0xffffffff): Virtual hotplug slot
  (empty)

(pcscd prints the following lines)
96781613 winscard_msg_srv.c:230:ProcessEventsServer() Common channel
packet arrival
00000037 winscard_msg_srv.c:242:ProcessEventsServer()
ProcessCommonChannelRequest detects: 4
00000173 pcscdaemon.c:93:SVCServiceRunLoop() A new context thread
creation is requested: 4
00000149 winscard_svc.c:297:ContextThread() Thread is started:
dwClientID=4, threadContext @0x8d86f20
00000019 winscard_svc.c:315:ContextThread() Received command:
CMD_VERSION from client 4
00000084 winscard_svc.c:327:ContextThread() Client is protocol version 4:2
00000095 winscard_svc.c:347:ContextThread() CMD_VERSION rv=0x0 for client 4
00000163 winscard_svc.c:315:ContextThread() Received command:
ESTABLISH_CONTEXT from client 4
00000092 winscard.c:193:SCardEstablishContext() Establishing Context:
0x1030AAC
00000015 winscard_svc.c:408:ContextThread() ESTABLISH_CONTEXT rv=0x0 for
client 4
00000156 winscard_svc.c:315:ContextThread() Received command:
CMD_GET_READERS_STATE from client 4
00000125 winscard_svc.c:315:ContextThread() Received command:
CMD_GET_READERS_STATE from client 4
00000570 winscard_svc.c:315:ContextThread() Received command:
RELEASE_CONTEXT from client 4
00000019 winscard.c:204:SCardReleaseContext() Releasing Context: 0x1030AAC
00000090 winscard_svc.c:423:ContextThread() RELEASE_CONTEXT rv=0x0 for
client 4
00000774 winscard_svc.c:307:ContextThread() Client die: 4
00000023 winscard_svc.c:918:MSGCleanupClient() Thread is stopping:
dwClientID=4, threadContext @0x8d86f20
00000085 winscard_svc.c:924:MSGCleanupClient() Freeing SCONTEXT @0x8d86f20

So it seems Cryptomate64 is *not* (yet, I hope...) supported :(

Is there something I can do to make it supported?

Tks.

BYtE,
 Diego.
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to