Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Hello, 2012/12/12 Rns Course rns_cou...@yahoo.com: (2) You said: installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). Is this really needed on unix? I thought pcscd would use its own libccid.so for this reader. Apparently not! The Omnikey CardMan 3121 reader is supported by my CCID driver. See http://pcsclite.alioth.debian.org/ccid/supported.html#0x076B0x3021 The vmware virtual reader is also supported by my CCID driver. See http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x0E0F0x0004 If this is a vendor provided library, what version are you using? Can you try without this file? Version 3.7.0, I added smartcard-list.txt on Dr. Ludovic Rousseau site that caused pcsc_scan recognizes my card (SmartCafe Expert 3.2 72k). It seems there was no need to ifdokccid.so driver! ifdokccid.so should not be needed. But it should not create problems if you install it and should be used by pcscd instead of my libccid driver. I am happy your problem is now fixed by a correct configuration of OpenSC. Bye -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
I must use muscle 0.9.11 because the javacard version of my card is 2.2.1. Muscle 0.9.12 uses version 2.2.2. I think that should compile opensc-0.11.3 on windows to work with muscle 0.9.11! Oh From: Douglas E. Engert deeng...@anl.gov To: Rns Course rns_cou...@yahoo.com Sent: Tuesday, 11 December 2012, 22:55:17 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! Just wanted to know if you got this e-mail, as it looks like your original problem is OpenSC does not support the old Muscle 0.9.11. You would have to use a newer version of the Muscle applet. Original Message Subject: Muscle smart card Applet various versions from M.U.S.C.L.E. and OpenSC Date: Mon, 10 Dec 2012 14:31:32 -0600 From: Douglas E. Engert deeng...@anl.gov To: MUSCLE mus...@lists.musclecard.com, OpenSC-devel opensc-devel@lists.opensc-project.org I am not using the Muscle card applet, but was looking looking at the OpenSC debug log for this thread: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! The OpenSC card-muscle.c (0.12.2 or 0.13.0) is looking for PROTO_VERSION_MAJOR=1 The author of the original note said: I've loaded and initialized Muscle applet (0.9.11) on it. This appears in the log that GET_STATUS is returning: 00 01 00 05 ... i.e. PROTO_VERSION_MAJOR=0, PROTO_VERSION_MINOR=1 This version from 2003-12-19, does not sound like the latest to me... Yet in the Muscle CVS archives: http://anonscm.debian.org/viewvc/muscleplugins/trunk/MCardApplet/ as of 4 years ago has version.properties has: APPLET_VERSION_MAJOR=0 APPLET_VERSION_MINOR=9 PROTO_VERSION_MAJOR=1 PROTO_VERSION_MINOR=3 And there have been changes in the SVN 9 months ago, 2 years ago and 3 years ago, which are not reflected in the Download page: https://alioth.debian.org/frs/?group_id=30111 Can the download versions be update, or the page change to say compile it yourself? Or point to the OpenSC page? Then on OpenSC-project: http://www.opensc-project.org/opensc/wiki/MuscleApplet it says: OpenSC supports the Muscle applet, available from Debian SVN: svn co svn://svn.debian.org/muscleplugins/trunk/MCardApplet (This appears to be the same SVN as on the Muscle page, revision 298 from 9 months ago.) An updated version, targeting recent JavaCard 2.2.2 cards with extended APDUs is available from github: http://github.com/martinpaljak/MuscleApplet This github is 3 years old, yet changes where made to the Muscle SVN 9 months ago. https://github.com/martinpaljak/MuscleApplet/blob/master/src/com/musclecard/CardEdge/CardEdge.java (3 years old) buffer[pos++] = (byte) 1; // Major Card Edge Protocol version n. buffer[pos++] = (byte) 3; // Minor Card Edge Protocol version n. buffer[pos++] = (byte) 0; // Major Applet version n. buffer[pos++] = (byte) 9; // Minor Applet version n. Which is in line with the PROTO_VERSION_MAJOR the OpenSC code is looking for. Can Martin and Ludovic get together and get these versions in sync, and make it so others don't download the 9 year old version? Thanks. -- Douglas E. Engert deeng...@anl.gov Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Hello and thanks for your complete and useful comment;
(1) VMware remaps the card card name, and causes confusion with pcsc.
If you could use a real machine that would eliminate this problem for
now.
I've switched to linux just because of testing pkcs15-init (opensc-0.12.2) in
it as an alternative work, since I didn't success in windows (with
opensc-0.12.2 0.13.0).
I only want to initialize the card using pkcs15-init ( Windows or Linux? It's
not important. I can test on windows completely! )
Now, I'm going to test the card with opensc-0.13.0 on windows only.
(2) You said:
installed Card Reader driver on fedora with name ifdokccid.so
(my Card Reader is Omnikey CardMan 3121).
Is this really needed on unix? I thought pcscd would use its own
libccid.so for this reader.
Apparently not!
If this is a vendor provided library, what version are you using? Can you
try without this file?
Version 3.7.0, I added smartcard-list.txt on Dr. Ludovic Rousseau site that
caused pcsc_scan recognizes my card (SmartCafe Expert 3.2 72k).
It seems there was no need to ifdokccid.so driver!
(3) You said:
I've tested OpenSC-0.13.0 MSI on Windows7 and had the same problem in
pkcs15 initialization as 0.12.2 version!
This would indicate that your real problem is with opensc most likely
not recognizing the card. (The vendor's window driver works with windows
but the vendor's unix driver may not work with the version of pcscd on
fedora. The introduction of VMware just complicates the problems.
Yes, exactly.
(4) You said the card is reported:
ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4
SmartCafe Expert 3.2 72K
I don't think this card is supported by OpenSC. In the OpenSC source, any
version
look at the src/libopensc directory. The supported cards all have a module
names card-*.c It might be possible that the iso7816.c directly.
Or you could add an entry in the opensc.conf to force the ATR to be mapped
to a specific supported card.
Yes, I did it.
My entry in opensc.conf:
card_atr 3b:f7:18:00:00:80:31:fe:45:73:66:74:65:2d:6e:66:c4 {
name = MyCard;
driver = muscle;
}
See the discussion from Aug 2011 on the OpenSC -devel lists:
[opensc-devel] SmartCafe Expert 3.2 72K works fine in some versions but is
an unsupported card in other versions.
It is not clear if this was ever resolved.
I already had his problem too. I solved it by putting muscle.profile in
profiles folder of opensc installation directory.
Thanks again.
From: Douglas E. Engert deeng...@anl.gov
To: opensc-devel@lists.opensc-project.org
Sent: Monday, 10 December 2012, 19:24:53
Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual
USB CCID 00 00 in linux ??!!
On 12/9/2012 9:56 AM, Ludovic Rousseau wrote:
2012/12/9 Rns Course rns_cou...@yahoo.com:
Another request of you:
what's your opinion about windows version of opensc (0.12.2 or 0.13.0) and
the problem File not found in pkcs15 initialization?
Why use 0.13.0:
o 0.13.0 has many more fixes.
o You will get better responses from this list if you test with 0.13.0.
o Any fixes will be applied to 0.13.0,
You may be fighting 4 different problems:
(1) VMware remaps the card card name, and causes confusion with pcsc.
If you could use a real machine that would eliminate this problem for now.
(2) You said:
installed Card Reader driver on fedora with name ifdokccid.so
(my Card Reader is Omnikey CardMan 3121).
Is this really needed on unix? I thought pcscd would use its own
libccid.so for this reader. If this is a vendor provided library,
what version are you using?
Can you try without this file.
(3) You said:
I've tested OpenSC-0.13.0 MSI on Windows7 and had the same problem in
pkcs15 initialization as 0.12.2 version!
This would indicate that your real problem is with opensc most likely
not recognizing the card. (The vendor's window driver works with windows
but the venodor's unix driver may not work with the version of pcscd on
fedora. The introduction of VMware just complicates the problems.
(4) You said the card is reported:
ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4
SmartCafe Expert 3.2 72K
I don't think this card is supported by OpenSC. In the OpenSC source, any
version
look at the src/libopensc directory. The supported cards all have a module
names card-*.c It might be possible that the iso7816.c directly.
Or you could add an entry in the opensc.conf to force the ATR to be mapped
to a
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
On 12/9/2012 9:56 AM, Ludovic Rousseau wrote: 2012/12/9 Rns Course rns_cou...@yahoo.com: Another request of you: what's your opinion about windows version of opensc (0.12.2 or 0.13.0) and the problem File not found in pkcs15 initialization? Why use 0.13.0: o 0.13.0 has many more fixes. o You will get better responses from this list if you test with 0.13.0. o Any fixes will be applied to 0.13.0, You may be fighting 4 different problems: (1) VMware remaps the card card name, and causes confusion with pcsc. If you could use a real machine that would eliminate this problem for now. (2) You said: installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). Is this really needed on unix? I thought pcscd would use its own libccid.so for this reader. If this is a vendor provided library, what version are you using? Can you try without this file. (3) You said: I've tested OpenSC-0.13.0 MSI on Windows7 and had the same problem in pkcs15 initialization as 0.12.2 version! This would indicate that your real problem is with opensc most likely not recognizing the card. (The vendor's window driver works with windows but the venodor's unix driver may not work with the version of pcscd on fedora. The introduction of VMware just complicates the problems. (4) You said the card is reported: ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K I don't think this card is supported by OpenSC. In the OpenSC source, any version look at the src/libopensc directory. The supported cards all have a module names card-*.c It might be possible that the iso7816.c directly. Or you could add an entry in the opensc.conf to force the ATR to be mapped to a specific supported card. See the discussion from Aug 2011 on the OpenSC -devel lists: [opensc-devel] SmartCafe Expert 3.2 72K works fine in some versions but is an unsupported card in other versions. It is not clear if this was ever resolved. In a previous note you said: Opensc-tool doesn't find the card to show the ATR, because the card reader is not known for it as OMNIKEY. No idea. -- Douglas E. Engert deeng...@anl.gov Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
More on this. Looking at the trace you did send on 12/9/2012: line 418: 0x7fff706e5cc0 14:39:03.351 [pkcs15-tool] card.c:180:sc_connect_card: trying driver: muscle causes the muscle_match_card in card-muscle.c to try and select the muscle applet with APDU: 00 A4 04 00 05 A0 00 00 00 01 with response: 90 00 It then reads some version information for the applet on the card APDU: B0 3C 00 00 40 with response: 00 01 00 05 00 00 75 30 00 00 5E F6 02 02 00 00 90 00 It is Successful, but response[0] == 0x00, but muscle_match_card is looking for 0x01 so it does not recognize the applet. Can you check how you loaded the applet. On 12/10/2012 9:54 AM, Douglas E. Engert wrote: On 12/9/2012 9:56 AM, Ludovic Rousseau wrote: 2012/12/9 Rns Course rns_cou...@yahoo.com: Another request of you: what's your opinion about windows version of opensc (0.12.2 or 0.13.0) and the problem File not found in pkcs15 initialization? Why use 0.13.0: o 0.13.0 has many more fixes. o You will get better responses from this list if you test with 0.13.0. o Any fixes will be applied to 0.13.0, You may be fighting 4 different problems: (1) VMware remaps the card card name, and causes confusion with pcsc. If you could use a real machine that would eliminate this problem for now. (2) You said: installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). Is this really needed on unix? I thought pcscd would use its own libccid.so for this reader. If this is a vendor provided library, what version are you using? Can you try without this file. (3) You said: I've tested OpenSC-0.13.0 MSI on Windows7 and had the same problem in pkcs15 initialization as 0.12.2 version! This would indicate that your real problem is with opensc most likely not recognizing the card. (The vendor's window driver works with windows but the venodor's unix driver may not work with the version of pcscd on fedora. The introduction of VMware just complicates the problems. (4) You said the card is reported: ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K I don't think this card is supported by OpenSC. In the OpenSC source, any version look at the src/libopensc directory. The supported cards all have a module names card-*.c It might be possible that the iso7816.c directly. Or you could add an entry in the opensc.conf to force the ATR to be mapped to a specific supported card. See the discussion from Aug 2011 on the OpenSC -devel lists: [opensc-devel] SmartCafe Expert 3.2 72K works fine in some versions but is an unsupported card in other versions. It is not clear if this was ever resolved. In a previous note you said: Opensc-tool doesn't find the card to show the ATR, because the card reader is not known for it as OMNIKEY. No idea. -- Douglas E. Engert deeng...@anl.gov Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Thanks; opensc-tool can see the (virtual) reader. But failed to connect to the card. Now, what's the solution? From: Ludovic Rousseau ludovic.rouss...@gmail.com To: Rns Course rns_cou...@yahoo.com Cc: opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org Sent: Saturday, 8 December 2012, 15:54:22 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/7 Rns Course rns_cou...@yahoo.com: Ludovic had said it was strange that pcsc_scan worked but opensc-tool -a did not. Pcsc_scan finds the reader as Virtual CCID not OMNIKEY, but gets the card's ATR correctly. Opensc-tool doesn't find the card to show the ATR, because the card reader is not known for it as OMNIKEY. opensc-tool will use any connected reader. Unless you gave a specific name but that was not explicit in your first email. opensc-tool can see the (virtual) reader. But failed to connect to the card. Bye -- Dr. Ludovic Rousseau___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
2012/12/9 Rns Course rns_cou...@yahoo.com: Thanks; opensc-tool can see the (virtual) reader. But failed to connect to the card. Now, what's the solution? Debug the problem. Generate a pcscd trace as described in [1] for the opensc-tool -a command. Bye [1] http://pcsclite.alioth.debian.org/pcsclite.html#support -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Hello Here's the trace: +++ Versions smart card reader driver name and version: The output of pcsc_scan: VMware Virtual USB CCID 00 00 (ifdokccid_lnx_i686-3.7.0) -- pcsc-lite version: The output of the command pcscd -v: 1.8.2 -- smart card reader name: (HID) Omnikey CardMan 3121 - the output of the command /usr/sbin/pcscd --version: pcsc-lite version 1.7.4. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux i386-redhat-linux-gnu serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d +++ Platform Operating system name and version: Fedora 16 (x86) Smart card middleware name and version: Muscle Applet (CardEdge.cap 0.9.11) Reader manufacturer name and reader model name: Omnikey cardMan 3121 Smart card name: GD SmartCafe Expert 3.2 72k +++ Also I've attached opensc-debug.log and log.txt to this email. I guess the problem is because of pcscd version (1.8.2 or 1.7.4)?! Am I right? (It's confusing!!) Best Regards. From: Ludovic Rousseau ludovic.rouss...@gmail.com To: Rns Course rns_cou...@yahoo.com Cc: opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org Sent: Sunday, 9 December 2012, 12:42:24 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/9 Rns Course rns_cou...@yahoo.com: Thanks; opensc-tool can see the (virtual) reader. But failed to connect to the card. Now, what's the solution? Debug the problem. Generate a pcscd trace as described in [1] for the opensc-tool -a command. Bye [1] http://pcsclite.alioth.debian.org/pcsclite.html#support -- Dr. Ludovic Rousseau debuglog.c:269:DebugLogSetLevel() debug level=debug 0035 debuglog.c:298:DebugLogSetCategory() Debug options: APDU 0831 configfile.l:245:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d 0911 configfile.l:287:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin 1102 configfile.l:124:evaluatetoken() Error with device JCOP_SIMUL_RDR: No such file or directory 1106 configfile.l:125:evaluatetoken() You should remove the DEVICENAME line if your driver does not use this field 00011763 configfile.l:287:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin~ 00011886 configfile.l:124:evaluatetoken() Error with device JCOP_SIMUL_RDR: No such file or directory 00011891 configfile.l:125:evaluatetoken() You should remove the DEVICENAME line if your driver does not use this field 00011929 pcscdaemon.c:657:at_exit() cleaning /var/run/pcscd 00011955 pcscdaemon.c:683:clean_temp_files() Cannot remove /var/run/pcscd/pcscd.comm: No such file or directory 00011978 pcscdaemon.c:657:at_exit() cleaning /var/run/pcscd 00011987 pcscdaemon.c:683:clean_temp_files() Cannot remove /var/run/pcscd/pcscd.comm: No such file or directory 00011994 pcscdaemon.c:689:clean_temp_files() Cannot remove /var/run/pcscd/pcscd.pid: No such file or directory opensc-debug.log Description: Binary data ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
2012/12/9 Rns Course rns_cou...@yahoo.com: Hello Here's the trace: +++ Versions smart card reader driver name and version: The output of pcsc_scan: VMware Virtual USB CCID 00 00 (ifdokccid_lnx_i686-3.7.0) -- pcsc-lite version: The output of the command pcscd -v: 1.8.2 I can't believe pcscd -v returned only one line. the output of the command /usr/sbin/pcscd --version: pcsc-lite version 1.7.4. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux i386-redhat-linux-gnu serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d And now you have a different version of pcscd. I guess the problem is because of pcscd version (1.8.2 or 1.7.4)?! Am I right? (It's confusing!!) Your pcsc-lite configuration is completely broken. Recreate a clean fedora 16 virtual machine from zero and try again. Bye -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
I can't believe pcscd -v returned only one line. No, returned the following result. but I put only first line. pcsc-lite version 1.8.2. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux i686-pc-linux-gnu serial usb libudev usbdropdir=/usr/local/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/usr/local/etc/reader.conf.d Your pcsc-lite configuration is completely broken. Recreate a clean fedora 16 virtual machine from zero and try again. Yes, Thank you. The problem is due to pcsclite. Your pcsc trace template that linked it, gave me the clue! Probably, I'll test it on OpenSUSE ASAP and tell the result here. Another request of you: what's your opinion about windows version of opensc (0.12.2 or 0.13.0) and the problem File not found in pkcs15 initialization? Sincerely. From: Ludovic Rousseau ludovic.rouss...@gmail.com To: Rns Course rns_cou...@yahoo.com Cc: opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org Sent: Sunday, 9 December 2012, 17:37:49 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/9 Rns Course rns_cou...@yahoo.com: Hello Here's the trace: +++ Versions smart card reader driver name and version: The output of pcsc_scan: VMware Virtual USB CCID 00 00 (ifdokccid_lnx_i686-3.7.0) -- pcsc-lite version: The output of the command pcscd -v: 1.8.2 I can't believe pcscd -v returned only one line. the output of the command /usr/sbin/pcscd --version: pcsc-lite version 1.7.4. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux i386-redhat-linux-gnu serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d And now you have a different version of pcscd. I guess the problem is because of pcscd version (1.8.2 or 1.7.4)?! Am I right? (It's confusing!!) Your pcsc-lite configuration is completely broken. Recreate a clean fedora 16 virtual machine from zero and try again. Bye -- Dr. Ludovic Rousseau___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
2012/12/9 Rns Course rns_cou...@yahoo.com: Another request of you: what's your opinion about windows version of opensc (0.12.2 or 0.13.0) and the problem File not found in pkcs15 initialization? No idea. -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Page #2 of the following document shows what the *real* problem is: http://webpki.org/papers/keygen2/sks-keygen2-exec-level-presentation.pdf Anders http://code.google.com/p/openkeystore ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
2012/12/7 Rns Course rns_cou...@yahoo.com: Ludovic had said it was strange that pcsc_scan worked but opensc-tool -a did not. Pcsc_scan finds the reader as Virtual CCID not OMNIKEY, but gets the card's ATR correctly. Opensc-tool doesn't find the card to show the ATR, because the card reader is not known for it as OMNIKEY. opensc-tool will use any connected reader. Unless you gave a specific name but that was not explicit in your first email. opensc-tool can see the (virtual) reader. But failed to connect to the card. Bye -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Hello In addition to trying to connect the card directly to the VM, you said you had built OpenSC-0.12.2. Could you try and build the new 0.13.0 and test again? Yes, I had built OpenSC-0.12.2 in linux (fedora 16) and wanted to initialize the card with pkcs15-init tool, but I was problem in connecting the card to the VM directly! The VM recognizes the card as shared reader not any USB device, So OpenSC-0.13.0 test would not be successful too! I've tested OpenSC-0.13.0 MSI on Windows7 and had the same problem in pkcs15 initialization as 0.12.2 version! If I could initialize the card in linux or windows by any version of opensc, my problem was resolved... Then because I had no success on windows using 0.13.0 and 0.12.2, I would try linux on VM. but the shared reader icon in VM doesn't let linux to recognize the reader as Omnikey CardMan 3x21 !! Ludovic had said it was strange that pcsc_scan worked but opensc-tool -a did not. Pcsc_scan finds the reader as Virtual CCID not OMNIKEY, but gets the card's ATR correctly. Opensc-tool doesn't find the card to show the ATR, because the card reader is not known for it as OMNIKEY. If you could post some debugging output for OpenSC-0.13.0, that would be helpful. Debug info for OpenSC-0.13.0 on Windows is same as OpenSC-0.12.2 that the main reason is File not found as I had sent before. But since the VMware is changing the name on the card, (and maybe idVendor and idPproduct) things might not work as expected. How the VM should be set to not change the name? Thanks beforehand for your helps; From: Douglas E. Engert deeng...@anl.gov To: opensc-devel@lists.opensc-project.org Sent: Wednesday, 5 December 2012, 19:06:34 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! On 12/5/2012 8:55 AM, Rns Course wrote: Thank you Dr. Rousseau, It is also possible to connect your reader directly to the VM as any other USB device. It will then not be available from Windows. Yes, exactly! My problem is because of not disconnecting card reader from windows. Now, how should I connect the reader directly to the VM as any USB device? Since, upon connecting the reader to system, shared reader icon appears on the VM task bar! Indeed, I have problem in VM setting to recognize the reader just as a USB device. Could you guide me about this? Best Regards. In addition to trying to connect the card directly to the VM, you said you had built OpenSC-0.12.2. Could you try and build the new 0.13.0 and test again? Tarball and MSI installers can be found on github, sourceforge or the CI server: https://github.com/OpenSC/OpenSC/tags https://sourceforge.net/projects/opensc/files/OpenSC/ https://opensc.fr/jenkins/ Ludovic had said it was strange that pcsc_scan worked but opensc-tool -a did not. If you could post some debugging output for OpenSC-0.13.0, that would be helpful. Either (1) modify the opensc.conf, changing the debug = 0; to debug = 7; and uncomment the debug_file = line. (2) add a -v option to the opensc-tool command line and output would be directed to stderr. Although then vendor provided the ifdokccid.so driver, it might not be needed as PCSClite says it is supported as CCID. But since the VMware is changing the name on the card, (and maybe idVendor and idPproduct) things might not work as expected. *From:* Ludovic Rousseau ludovic.rouss...@gmail.com *To:* opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org *Sent:* Wednesday, 5 December 2012, 16:51:28 *Subject:* Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/5 Rns Course rns_cou...@yahoo.com mailto:rns_cou...@yahoo.com: Hi all; Hello, I have a smart card (SmartCafe Expert 3.2 72k) and I've loaded and initialized Muscle applet (0.9.11) on it. Now, I have problem with pkcs15 initializing... In Windows, I couldn't initialize the card using pkcs15-init tool, so I decided to compile opensc-0.12.2 in linux (fedora 16) and use pkcs15-init tool in linux. I have fedora on VMWare ( my host OS is Windows7) and installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). I've got and installed pcsc-tools package on linux and run pcsc_scan command on Terminal, the output was as below: --- PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr mailto:ludovic.rouss...@free.fr Compiled with PC/SC lite version:
[opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Hi all; I have a smart card (SmartCafe Expert 3.2 72k) and I've loaded and initialized Muscle applet (0.9.11) on it. Now, I have problem with pkcs15 initializing... In Windows, I couldn't initialize the card using pkcs15-init tool, so I decided to compile opensc-0.12.2 in linux (fedora 16) and use pkcs15-init tool in linux. I have fedora on VMWare ( my host OS is Windows7) and installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). I've got and installed pcsc-tools package on linux and run pcsc_scan command on Terminal, the output was as below: --- PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.6.6 Scanning present readers... 0: VMware Virtual USB CCID 00 00 Wed Dec 5 11:03:39 2012 Reader 0: VMware Virtual USB CCID 00 00 Card state: Card inserted, ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 + TS = 3B -- Direct Convention + T0 = F7, Y(1): , K: 7 (historical bytes) TA(1) = 18 -- Fi=372, Di=12, 31 cycles/ETU 129032 bits/s at 4 MHz, fMax for Fi = 5 MHz = 161290 bits/s TB(1) = 00 -- VPP is not electrically connected TC(1) = 00 -- Extra guard time: 0 TD(1) = 80 -- Y(i+1) = 1000, Protocol T = 0 - TD(2) = 31 -- Y(i+1) = 0011, Protocol T = 1 - TA(3) = FE -- IFSC: 254 TB(3) = 45 -- Block Waiting Integer: 4 - Character Waiting Integer: 5 + Historical bytes: 73 66 74 65 2D 6E 66 Category indicator byte: 73 (proprietary format) + TCK = C4 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K -- My problem is that VMWare finds the reader as: Reader 0: VMware Virtual USB CCID 00 00 NOT Reader 0: Omnikey CardMan 3121 00 00 !! So, the command opensc-tool -a has the following output: Using reader with a card: VMware Virtual USB CCID 00 00 Failed to connect to card: Unresponsive card (correctly inserted?) When I connect the reader to the system, VMWare recognizes it as : Shared OMNIKEY CardMan 3x21 0 in Removable Devices section of VM, so fedora finds it as VMware Virtual USB CCID 00 00 reader not Omnikey! How should the card reader be introduced in VM to solve this problem? I guess the problem is because of VMWare settings for card reader not OpenSC, but I've not found more related forum than here to ask this question; Could you help me please? TIA.___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
2012/12/5 Rns Course rns_cou...@yahoo.com: Hi all; Hello, I have a smart card (SmartCafe Expert 3.2 72k) and I've loaded and initialized Muscle applet (0.9.11) on it. Now, I have problem with pkcs15 initializing... In Windows, I couldn't initialize the card using pkcs15-init tool, so I decided to compile opensc-0.12.2 in linux (fedora 16) and use pkcs15-init tool in linux. I have fedora on VMWare ( my host OS is Windows7) and installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). I've got and installed pcsc-tools package on linux and run pcsc_scan command on Terminal, the output was as below: --- PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.6.6 Scanning present readers... 0: VMware Virtual USB CCID 00 00 Wed Dec 5 11:03:39 2012 Reader 0: VMware Virtual USB CCID 00 00 Card state: Card inserted, ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 + TS = 3B -- Direct Convention + T0 = F7, Y(1): , K: 7 (historical bytes) TA(1) = 18 -- Fi=372, Di=12, 31 cycles/ETU 129032 bits/s at 4 MHz, fMax for Fi = 5 MHz = 161290 bits/s TB(1) = 00 -- VPP is not electrically connected TC(1) = 00 -- Extra guard time: 0 TD(1) = 80 -- Y(i+1) = 1000, Protocol T = 0 - TD(2) = 31 -- Y(i+1) = 0011, Protocol T = 1 - TA(3) = FE -- IFSC: 254 TB(3) = 45 -- Block Waiting Integer: 4 - Character Waiting Integer: 5 + Historical bytes: 73 66 74 65 2D 6E 66 Category indicator byte: 73 (proprietary format) + TCK = C4 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K -- My problem is that VMWare finds the reader as: Reader 0: VMware Virtual USB CCID 00 00 NOT Reader 0: Omnikey CardMan 3121 00 00 !! So, the command opensc-tool -a has the following output: Using reader with a card: VMware Virtual USB CCID 00 00 Failed to connect to card: Unresponsive card (correctly inserted?) When I connect the reader to the system, VMWare recognizes it as : Shared OMNIKEY CardMan 3x21 0 in Removable Devices section of VM, so fedora finds it as VMware Virtual USB CCID 00 00 reader not Omnikey! How should the card reader be introduced in VM to solve this problem? I guess the problem is because of VMWare settings for card reader not OpenSC, but I've not found more related forum than here to ask this question; Could you help me please? VMWare uses a trick to show the smart card reader in the VM without disconnecting it from the host. VMWare uses PC/SC on Windows to access the reader and shows it as a fake CCID reader in the VM. It is strange that you can get the ATR using pcsc_scan but not using opensc-tool -a. It is also possible to connect your reader directly to the VM as any other USB device. It will then not be available from Windows. Bye -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
Thank you Dr. Rousseau, It is also possible to connect your reader directly to the VM as any other USB device. It will then not be available from Windows. Yes, exactly! My problem is because of not disconnecting card reader from windows. Now, how should I connect the reader directly to the VM as any USB device? Since, upon connecting the reader to system, shared reader icon appears on the VM task bar! Indeed, I have problem in VM setting to recognize the reader just as a USB device. Could you guide me about this? Best Regards. From: Ludovic Rousseau ludovic.rouss...@gmail.com To: opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org Sent: Wednesday, 5 December 2012, 16:51:28 Subject: Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/5 Rns Course rns_cou...@yahoo.com: Hi all; Hello, I have a smart card (SmartCafe Expert 3.2 72k) and I've loaded and initialized Muscle applet (0.9.11) on it. Now, I have problem with pkcs15 initializing... In Windows, I couldn't initialize the card using pkcs15-init tool, so I decided to compile opensc-0.12.2 in linux (fedora 16) and use pkcs15-init tool in linux. I have fedora on VMWare ( my host OS is Windows7) and installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). I've got and installed pcsc-tools package on linux and run pcsc_scan command on Terminal, the output was as below: --- PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.6.6 Scanning present readers... 0: VMware Virtual USB CCID 00 00 Wed Dec 5 11:03:39 2012 Reader 0: VMware Virtual USB CCID 00 00 Card state: Card inserted, ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 + TS = 3B -- Direct Convention + T0 = F7, Y(1): , K: 7 (historical bytes) TA(1) = 18 -- Fi=372, Di=12, 31 cycles/ETU 129032 bits/s at 4 MHz, fMax for Fi = 5 MHz = 161290 bits/s TB(1) = 00 -- VPP is not electrically connected TC(1) = 00 -- Extra guard time: 0 TD(1) = 80 -- Y(i+1) = 1000, Protocol T = 0 - TD(2) = 31 -- Y(i+1) = 0011, Protocol T = 1 - TA(3) = FE -- IFSC: 254 TB(3) = 45 -- Block Waiting Integer: 4 - Character Waiting Integer: 5 + Historical bytes: 73 66 74 65 2D 6E 66 Category indicator byte: 73 (proprietary format) + TCK = C4 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K -- My problem is that VMWare finds the reader as: Reader 0: VMware Virtual USB CCID 00 00 NOT Reader 0: Omnikey CardMan 3121 00 00 !! So, the command opensc-tool -a has the following output: Using reader with a card: VMware Virtual USB CCID 00 00 Failed to connect to card: Unresponsive card (correctly inserted?) When I connect the reader to the system, VMWare recognizes it as : Shared OMNIKEY CardMan 3x21 0 in Removable Devices section of VM, so fedora finds it as VMware Virtual USB CCID 00 00 reader not Omnikey! How should the card reader be introduced in VM to solve this problem? I guess the problem is because of VMWare settings for card reader not OpenSC, but I've not found more related forum than here to ask this question; Could you help me please? VMWare uses a trick to show the smart card reader in the VM without disconnecting it from the host. VMWare uses PC/SC on Windows to access the reader and shows it as a fake CCID reader in the VM. It is strange that you can get the ATR using pcsc_scan but not using opensc-tool -a. It is also possible to connect your reader directly to the VM as any other USB device. It will then not be available from Windows. Bye -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!!
On 12/5/2012 8:55 AM, Rns Course wrote: Thank you Dr. Rousseau, It is also possible to connect your reader directly to the VM as any other USB device. It will then not be available from Windows. Yes, exactly! My problem is because of not disconnecting card reader from windows. Now, how should I connect the reader directly to the VM as any USB device? Since, upon connecting the reader to system, shared reader icon appears on the VM task bar! Indeed, I have problem in VM setting to recognize the reader just as a USB device. Could you guide me about this? Best Regards. In addition to trying to connect the card directly to the VM, you said you had built OpenSC-0.12.2. Could you try and build the new 0.13.0 and test again? Tarball and MSI installers can be found on github, sourceforge or the CI server: https://github.com/OpenSC/OpenSC/tags https://sourceforge.net/projects/opensc/files/OpenSC/ https://opensc.fr/jenkins/ Ludovic had said it was strange that pcsc_scan worked but opensc-tool -a did not. If you could post some debugging output for OpenSC-0.13.0, that would be helpful. Either (1) modify the opensc.conf, changing the debug = 0; to debug = 7; and uncomment the debug_file = line. (2) add a -v option to the opensc-tool command line and output would be directed to stderr. Although then vendor provided the ifdokccid.so driver, it might not be needed as PCSClite says it is supported as CCID. But since the VMware is changing the name on the card, (and maybe idVendor and idPproduct) things might not work as expected. *From:* Ludovic Rousseau ludovic.rouss...@gmail.com *To:* opensc-devel@lists.opensc-project.org opensc-devel@lists.opensc-project.org *Sent:* Wednesday, 5 December 2012, 16:51:28 *Subject:* Re: [opensc-devel] The smart card reader is known as VMware Virtual USB CCID 00 00 in linux ??!! 2012/12/5 Rns Course rns_cou...@yahoo.com mailto:rns_cou...@yahoo.com: Hi all; Hello, I have a smart card (SmartCafe Expert 3.2 72k) and I've loaded and initialized Muscle applet (0.9.11) on it. Now, I have problem with pkcs15 initializing... In Windows, I couldn't initialize the card using pkcs15-init tool, so I decided to compile opensc-0.12.2 in linux (fedora 16) and use pkcs15-init tool in linux. I have fedora on VMWare ( my host OS is Windows7) and installed Card Reader driver on fedora with name ifdokccid.so (my Card Reader is Omnikey CardMan 3121). I've got and installed pcsc-tools package on linux and run pcsc_scan command on Terminal, the output was as below: --- PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr mailto:ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.6.6 Scanning present readers... 0: VMware Virtual USB CCID 00 00 Wed Dec 5 11:03:39 2012 Reader 0: VMware Virtual USB CCID 00 00 Card state: Card inserted, ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 ATR: 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 + TS = 3B -- Direct Convention + T0 = F7, Y(1): , K: 7 (historical bytes) TA(1) = 18 -- Fi=372, Di=12, 31 cycles/ETU 129032 bits/s at 4 MHz, fMax for Fi = 5 MHz = 161290 bits/s TB(1) = 00 -- VPP is not electrically connected TC(1) = 00 -- Extra guard time: 0 TD(1) = 80 -- Y(i+1) = 1000, Protocol T = 0 - TD(2) = 31 -- Y(i+1) = 0011, Protocol T = 1 - TA(3) = FE -- IFSC: 254 TB(3) = 45 -- Block Waiting Integer: 4 - Character Waiting Integer: 5 + Historical bytes: 73 66 74 65 2D 6E 66 Category indicator byte: 73 (proprietary format) + TCK = C4 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B F7 18 00 00 80 31 FE 45 73 66 74 65 2D 6E 66 C4 SmartCafe Expert 3.2 72K -- My problem is that VMWare finds the reader as: Reader 0: VMware Virtual USB CCID 00 00 NOT Reader 0: Omnikey CardMan 3121 00 00 !! So, the command opensc-tool -a has the following output: Using reader with a card: VMware Virtual USB CCID 00 00 Failed to connect to card: Unresponsive card (correctly inserted?) When I connect the reader to the system, VMWare recognizes it as : Shared OMNIKEY CardMan 3x21 0 in Removable Devices section of VM, so fedora finds it as VMware Virtual USB CCID 00 00 reader not Omnikey! How should the card reader be introduced in VM to solve this problem? I guess the problem is because of VMWare settings for card
