On 11/4/2011 6:09 AM, anze.stojilko...@policija.si wrote:
I modified opensc.conf and I added this:

card_atr 
3b:ff:13:00:00:81:31:fe:4d:80:25:a0:00:00:00:56:57:44:4b:33:33:30:06:00:d2 {
name = "PIV-II";
driver = "muscle";

This is forcing the the muscle driver to use the card, but
the card is not a muscle card, thus the unsupported card
message, and also bypassing where ever the segfault was at.

Rather doing this, can you remove those lines, and change these lines
to turn on debugging to a file:

--- opensc.conf.new     Fri Sep 23 11:00:35 2011
+++ opensc.conf Wed May 11 16:10:52 2011
@@ -12,14 +12,16 @@
        # A greater value means more debug info.
        # Default: 0
        #
-       debug = 0;
+debug = 7;
+#debug = 0;
+

        # The file to which debug output will be written
        #
        # Special values 'stdout' and 'stderr' are recognized.
        # Default: stderr
        #
-       # debug_file = /tmp/opensc-debug.log;
+ debug_file = /tmp/opensc-debug.log;
        # debug_file = "C:\Documents and Settings\All 
Users\Documents\opensc-debug.log";

        # PKCS#15 initialization / personalization
@@ -447,7 +449,6 @@
        }
 }

Then run the tests again, and send the debug output to the
list or myself?

Each command will append to the debug file, so if you run more then one
command, you may want to copy the file between commands and send separate
files.  The debug trace may show what is was doing just before the segfault.


And now, there is no segmentation fault, but I am still not sure which card 
driver do I have to use.

This may be a PIV card as they appear to sell them, but it is not
initialized in any way, and the code may not have anticipated such
a card being used.


According to ATR, my card is:
Possibly identified card: Datakey DCOS model 330 (DKCCOS 6.0 token)

# Now, pkcs11-tool --module <path/to/opensc-pkcs11.so>-L gives me this:
[opensc-pkcs11] pkcs15.c:799:sc_pkcs15_bind: returning with: Unsupported card
Available slots:
Slot 0 (empty)
Slot 1 (empty)
Slot 2 (empty)
Slot 3 (empty)
Slot 4 (empty)
Slot 5 (empty)
Slot 6 (empty)
Slot 7 (empty)
Slot 8 (empty)
Slot 9 (empty)
Slot 10 (empty)
Slot 11 (empty)
Slot 12 (empty)
Slot 13 (empty)
Slot 14 (empty)
Slot 15 (empty)

# opensc-tool -l gives me this:
Readers known about:
Nr. Driver Name
0 openct OpenCT reader (detached)
1 openct OpenCT reader (detached)
2 pcsc OMNIKEY CardMan 3x21 00 00

# pkcs11-tool -I
[opensc-pkcs11] pkcs15.c:799:sc_pkcs15_bind: returning with: Unsupported card
Cryptoki version 2.20
Manufacturer OpenSC (www.opensc-project.org)
Library smart card PKCS#11 API (ver 0.0)

I hope those infos help you to know how to help me, becouse I am really stuck 
here.

Thank you





Od: "Douglas E. Engert" <deeng...@anl.gov>
Za: muscle@lists.musclecard.com
Datum: 26.10.2011 16:57
Zadeva: Re: [Muscle] SafeNet Smartcard 330
Poslal: muscle-boun...@lists.musclecard.com
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------



This discussion should be moved to <opensc-u...@lists.opensc-project.org> or
OpenSC-devel <opensc-de...@lists.opensc-project.org>

On 10/26/2011 2:37 AM, anze.stojilko...@policija.si wrote:
 > Yes, the system finds SafeNet card as PIV-II card*.*
 >
 > How can I initialize the card?

The intent of the OpenSC PIV card support is to support pre-issued
PIV cards by supporting the NIST 800-73 standards. These standards do
not define a full set of card management operations but leave that up
to the vendors. The PIV cards where not designed for user provisioning.

See: http://www.opensc-project.org/opensc/wiki/UnitedStatesPIV

But OpenSC has the piv-tool to allow a PIV card to be partially
initialized/provisioned for test purposes. It will require some commands
that are vendor specific. You will need to get these commands from the
card vendor, as well as any initial PINs and keys used during
initialization. Use of the piv-tool does not replace the need
for a good card management system.

SafeNet offers two card management products that may or may not work
with the PIV card.
http://www.safenet-inc.com/products/data-protection/two-factor-authentication/etoken-tms/
http://www.safenet-inc.com/products/data-protection/two-factor-authentication/myid-card-management-center/

 >
 > # opensc-tool -I> opensc 0.11.13 [gcc 4.5.0 20100604 [gcc-4_5-branch 
revision 160292]]
 > Enabled features: zlib readline iconv openssl openct 
pcsc(/usr/lib/libpcsclite.so.1) nsplugin
 >
 > # opensc-tool -a
 > Using reader with a card: OMNIKEY CardMan 3x21 00 00
 > 3b:ff:13:00:00:81:31:fe:4d:80:25:a0:00:00:00:56:57:44:4b:33:33:30:06:00:d2
 >
 > pkcs11-tool --module <path/to/opensc-pkcs11.so>-L still gives me 
Segmentation fault
 >
 > # gdb --args pkcs11-tool -I
 > GNU gdb (GDB) SUSE (7.1-3.12)
 > Copyright (C) 2010 Free Software Foundation, Inc.
 > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 > This is free software: you are free to change and redistribute it.
 > There is NO WARRANTY, to the extent permitted by law. Type "show copying"
 > and "show warranty" for details.
 > This GDB was configured as "i586-suse-linux".
 > For bug reporting instructions, please see:
 > <http://www.gnu.org/software/gdb/bugs/>...
 > Reading symbols from /usr/bin/pkcs11-tool...Missing separate debuginfo for 
/usr/bin/pkcs11-tool
 > Try: zypper install -C 
"debuginfo(build-id)=7034486b591f3d39c4066653d8c803b3f1740c3a"
 > (no debugging symbols found)...done.
 > (gdb) run
 > Starting program: /usr/bin/pkcs11-tool -I
 > Missing separate debuginfo for /lib/ld-linux.so.2
 > Try: zypper install -C 
"debuginfo(build-id)=22e2b3718e8271a0d899156a796b0a90bc4dc391"
 > Missing separate debuginfo for /usr/lib/libopensc.so.2
 > Try: zypper install -C 
"debuginfo(build-id)=a2968b909d9f77159f6ceac9e27292f40329cea2"
 > Missing separate debuginfo for /lib/libcrypto.so.1.0.0
 > Try: zypper install -C 
"debuginfo(build-id)=748b7a6af35635f6d49b3e490bc63326a29d90f4"
 > Missing separate debuginfo for /usr/lib/libltdl.so.7
 > Try: zypper install -C 
"debuginfo(build-id)=5b5598e8ebd310d83acde7a67ba6894627004523"
 > Missing separate debuginfo for /lib/libpthread.so.0
 > Try: zypper install -C 
"debuginfo(build-id)=ebd849d5f5cebe33657f871a32bf0eb34132e8d1"
 > [Thread debugging using libthread_db enabled]
 > Missing separate debuginfo for /lib/libc.so.6
 > Try: zypper install -C 
"debuginfo(build-id)=62a8bfd7732322fa6b9c39d39a830a8028804534"
 > Missing separate debuginfo for /usr/lib/libopenct.so.1
 > Try: zypper install -C 
"debuginfo(build-id)=f7efb05f0795f9f22db4a941c6c5cb93b3c0a0ee"
 > Missing separate debuginfo for /lib/libz.so.1
 > Try: zypper install -C 
"debuginfo(build-id)=afddd839a6c18dd308b04b5289c56cc3abd1384f"
 > Missing separate debuginfo for /usr/lib/libscconf.so.2
 > Try: zypper install -C 
"debuginfo(build-id)=a2730fd63a824c6c74d4405d741d1a15b6b912de"
 > Missing separate debuginfo for /lib/libdl.so.2
 > Try: zypper install -C 
"debuginfo(build-id)=20519b5f2874a1cf29e149802cfbef0db142633f"
 > Missing separate debuginfo for /usr/lib/opensc-pkcs11.so
 > Try: zypper install -C 
"debuginfo(build-id)=96f91af434b1fad440a1568057509c47e9b3ef6f"
 > Missing separate debuginfo for /usr/lib/libpkcs15init.so.2
 > Try: zypper install -C 
"debuginfo(build-id)=2c1a3b91716eb49aae5a31ba08c3e94caeacd221"
 > Missing separate debuginfo for /usr/lib/libpcsclite.so.1
 > Try: zypper install -C 
"debuginfo(build-id)=02dd0ec78d070922bcb6dbb7d47558f13ddb26a2"
 >
 > Program received signal SIGSEGV, Segmentation fault.
 > 0xb7f34bb7 in ?? () from /usr/lib/libopensc.so.2
 >

In addition to what Martin said about a newer version, and using the debuginfo,
The opensc.conf file has a number of debugging options that could help with
finding any problems:

15c15,17
< debug = 0;
---
 > debug = 7;
 > #debug = 0;
 >
22c24
< # debug_file = /tmp/opensc-debug.log;
---
 > debug_file = /tmp/opensc-debug.log;


 >
 > I really appreciate your help!
 >
 >
 >
 >
 > Od: "Douglas E. Engert" <deeng...@anl.gov>
 > Za: muscle@lists.musclecard.com
 > Datum: 25.10.2011 17:00
 > Zadeva: Re: [Muscle] SafeNet Smartcard 330
 > Poslal: muscle-boun...@lists.musclecard.com
 > 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 >
 >
 >
 >
 >
 > On 10/25/2011 8:42 AM, anze.stojilko...@policija.si wrote:
 > > Hi,
 > >
 > > Any suggestions on how can I get my SafeNet Smartcard 330 work on openSuse?
 > > I have installed opensc and pkcs11.
 > >
 > > - If I type opensc-tool -n it returns;
 >
 > >
 > > "Using reader with a card: OMNIKEY CardMan 3x21 00 00
 > > PIV-II card"
 >
 > So the SafeNet card looks like a PIV-II card???
 > Has the card been initialized?
 >
 > Do you have the ATR from the card? opensc-tool -a
 >
 > What version of OpenSC version?: opensc-tool -i
 >
 > >
 > > - pkcs11-tool --I returns;
 > >
 > > "Segmentation fault"
 >
 > With pkcs11-tool try the --module option to point to the opensc-pkcs11.so
 > the --module option that is required.
 > Then try it with the -L and -T and maybe the -O options.
 >
 > pkcs11-tool --module <path/to/opensc-pkcs11.so> -L
 >
 > If it still segfaults, try running with gdb:
 >
 > gdb --args pkcs11-tool -I
 > run
 >
 > >
 > >
 > > Sorry for lack of informations, but I am new on this and I don't know what 
you need to help me.
 > >
 > > Thank you for your help
 > >
 > >
 > > _______________________________________________
 > > Muscle mailing list
 > > Muscle@lists.musclecard.com
 > > http://lists.drizzle.com/mailman/listinfo/muscle
 >
 > --
 >
 > Douglas E. Engert <deeng...@anl.gov>
 > Argonne National Laboratory
 > 9700 South Cass Avenue
 > Argonne, Illinois 60439
 > (630) 252-5444
 > _______________________________________________
 > Muscle mailing list
 > Muscle@lists.musclecard.com
 > http://lists.drizzle.com/mailman/listinfo/muscle
 >
 >
 >
 > _______________________________________________
 > Muscle mailing list
 > Muscle@lists.musclecard.com
 > http://lists.drizzle.com/mailman/listinfo/muscle

--

Douglas E. Engert <deeng...@anl.gov>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle



_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

--

 Douglas E. Engert  <deeng...@anl.gov>
 Argonne National Laboratory
 9700 South Cass Avenue
 Argonne, Illinois  60439
 (630) 252-5444
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to