Co nieco o 3DES http://www.rsa.com/rsalabs/node.asp?id=2231
2013/1/11 <[email protected]>: > Send Muscle mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Muscle digest..." > > > Today's Topics: > > 1. Re: Identifyng a contact smartcard (Diego Delgado) > 2. Re: Identifyng a contact smartcard (Sebastien Lorquet) > 3. PC/SC issues with Aladdin eToken PRO 64 on Ubuntu Quetzal > (12.10) (Yoann Juet) > 4. Re: PC/SC issues with Aladdin eToken PRO 64 on Ubuntu Quetzal > (12.10) (Yoann Juet) > 5. Re: PC/SC issues with Aladdin eToken PRO 64 on Ubuntu Quetzal > (12.10) (Martin Paljak) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 11 Jan 2013 09:42:02 +0100 > From: Diego Delgado <[email protected]> > To: [email protected] > Subject: Re: [Muscle] Identifyng a contact smartcard > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > El 09/01/2013 17:34, helpcrypto helpcrypto escribi?: >> Hi Diego. >> >> Usually smartcards have some marks to help identify manufacturer, like >> Saetic, microelectr?nica, FNMT and so. >> With this marks and ATR you could go to manufacturer and ask. >> If you want, send a front and read photo and maybe i could help. >> >> According to standard 6D00 = Instruction code not supported or invalid. :( >> >> _______________________________________________ >> Muscle mailing list >> [email protected] >> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com > I think here we can contact with the manufacturer, I'll try this. > > Thanks! > > -- > Diego Delgado Roda > [email protected] > IDONEUM Electronic Identity, S.A. > Calmell Group > www.idoneum.net > Pol?gono Industrial Pla d?en Coll > C/ Fresser 12 C > 08110 MONTCADA I REIXAC (Barcelona) > Tel +34 93 564 14 00 > Fax +34 93 564 58 22 > > > > > ------------------------------ > > Message: 2 > Date: Fri, 11 Jan 2013 10:21:09 +0100 > From: Sebastien Lorquet <[email protected]> > To: MUSCLE <[email protected]> > Subject: Re: [Muscle] Identifyng a contact smartcard > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > Le 11/01/2013 09:42, Diego Delgado a ?crit : >> El 09/01/2013 17:34, helpcrypto helpcrypto escribi?: >>> Hi Diego. >>> >>> Usually smartcards have some marks to help identify manufacturer, like >>> Saetic, microelectr?nica, FNMT and so. >>> With this marks and ATR you could go to manufacturer and ask. >>> If you want, send a front and read photo and maybe i could help. >>> >>> According to standard 6D00 = Instruction code not supported or invalid. :( >>> >>> _______________________________________________ >>> Muscle mailing list >>> [email protected] >>> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com >> I think here we can contact with the manufacturer, I'll try this. >> >> Thanks! >> > If you can do that, it will be the most efficient solution to identify your > card, since the ATR is totally customizable and will vary greatly when you're > not dealing with a "mainline" product. > > Just thinking, a good thing to do on the Internet may be a micromodule image > database with manufacturer indications. Not totally reliable, but it would > provide useful indications in some cases. > > Regards > Sebastien > > > > ------------------------------ > > Message: 3 > Date: Fri, 11 Jan 2013 16:47:30 +0100 > From: Yoann Juet <[email protected]> > To: [email protected] > Subject: [Muscle] PC/SC issues with Aladdin eToken PRO 64 on Ubuntu > Quetzal (12.10) > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Hi all, > > We have used, on Ubuntu systems, cryptographic tokens 'Aladdin eToken > PRO 64' for ssh public key authentication for many years now. Since the > release of Ubuntu 12.10 aka Quantal Quetzal we're facing a major > problem. On a fresh installation of Quantal with all updates, when I try > to add keys provided by the PKCS#11 library to the ssh authentication > agent, I get the following error: > > irts~$ ssh-add -s /usr/lib/opensc-pkcs11.so > Enter passphrase for PKCS#11: > SSH_AGENT_FAILURE > Could not add card: /usr/lib/opensc-pkcs11.so > > irts~$ opensc-tool -l > # Detected readers (pcsc) > Nr. Card Features Name > 0 Yes Aladdin eToken PRO 64 00 00 > > The only workaround I found until now is stopping the service pcscd and > restarting it in foreground mode. Then, ssh-add authentication works as > expected: > > irts~$ sudo /etc/init.d/pcscd stop > irts~$ sudo pcscd -f > 00000000 dyn_unix.c:81:DYN_GetAddress() IFDHCreateChannelByName: > /usr/lib/pcsc/drivers/openct-ifd.bundle/Contents/Linux/openct-ifd.so: > undefined symbol: IFDHCreateChann > 00001577 ccid_usb.c:514:OpenUSBByName() Can't claim interface 2/5: -6 > 00000048 ifdhandler.c:117:CreateChannelByNameOrChannel() failed > 00000021 readerfactory.c:1009:RFInitializeReader() Open Port 0x200001 > Failed (usb:058f/9540:libudev:0:/dev/bus/usb/002/005) > 00000006 readerfactory.c:312:RFAddReader() Alcor Micro AU9540 init failed. > 00000027 hotplug_libudev.c:384:HPAddDevice() Failed adding USB device: > Alcor Micro AU9540 > 00000010 utils.c:95:CheckForOpenCT() File /var/run/openct/status found. > Remove OpenCT and try again > Error: Bad CTBCS APDU, ins=0x15 > > irts~$ ssh-add -s /usr/lib/opensc-pkcs11.so > Enter passphrase for PKCS#11: > Card added: /usr/lib/opensc-pkcs11.so > > This problems seems to be related to PC/SC. Do you have any hints on the > possible cause ? > > ---- > > ii libopenct1 0.6.20-1.2 > ii libpcsc-perl 1.4.12-1build2 > ii libpcsclite1:amd64 1.8.5-1ubuntu1 > ii openct 0.6.20-1.2 > ii opensc 0.12.2-2ubuntu2 > ii pcsc-tools 1.4.20-1 > ii pcscd 1.8.5-1ubuntu1 > ii libccid 1.4.7-1 > > Thanks for your assistance, > Regards, > -- > Universit? de Nantes - Direction des Syst?mes d'Information > Ing?nieur r?seau & s?curit? > IM jabber: [email protected] > T?l: 02.53.48.49.26 - Fax: 02.53.48.49.09 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: yoann_juet.vcf > Type: text/x-vcard > Size: 352 bytes > Desc: not available > URL: > <http://lists.musclecard.com/pipermail/muscle_lists.musclecard.com/attachments/20130111/468ab5b1/attachment-0001.vcf> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/pkcs7-signature > Size: 3256 bytes > Desc: S/MIME Cryptographic Signature > URL: > <http://lists.musclecard.com/pipermail/muscle_lists.musclecard.com/attachments/20130111/468ab5b1/attachment-0001.p7s> > > ------------------------------ > > Message: 4 > Date: Fri, 11 Jan 2013 17:41:47 +0100 > From: Yoann Juet <[email protected]> > To: Martin Paljak <[email protected]> > Cc: MUSCLE <[email protected]> > Subject: Re: [Muscle] PC/SC issues with Aladdin eToken PRO 64 on > Ubuntu Quetzal (12.10) > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > On 11/01/13 17:24, Martin Paljak wrote: >> >> Remove openct and libopenct1 packages. >> > > Martin, > > Thanks for your quick reply. I already tried this solution. It doesn't > work. My token is no more detected. PC/SC seems to need "etoken64" > driver provided by openct (cannot find Aladdin eToken PRO 64 in libccid > list of supported devices). > > -- > Universit? de Nantes - Direction des Syst?mes d'Information > Ing?nieur r?seau & s?curit? > IM jabber: [email protected] > T?l: 02.53.48.49.26 - Fax: 02.53.48.49.09 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: yoann_juet.vcf > Type: text/x-vcard > Size: 376 bytes > Desc: not available > URL: > <http://lists.musclecard.com/pipermail/muscle_lists.musclecard.com/attachments/20130111/76113d4f/attachment-0001.vcf> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/pkcs7-signature > Size: 3256 bytes > Desc: S/MIME Cryptographic Signature > URL: > <http://lists.musclecard.com/pipermail/muscle_lists.musclecard.com/attachments/20130111/76113d4f/attachment-0001.p7s> > > ------------------------------ > > Message: 5 > Date: Fri, 11 Jan 2013 18:24:21 +0200 > From: Martin Paljak <[email protected]> > To: [email protected], MUSCLE <[email protected]> > Subject: Re: [Muscle] PC/SC issues with Aladdin eToken PRO 64 on > Ubuntu Quetzal (12.10) > Message-ID: > <cacsm3dxcossb4ts7yycqlf1a3n7veuoc2qx4ogs51txywpa...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Fri, Jan 11, 2013 at 5:47 PM, Yoann Juet <[email protected]> wrote: > >> This problems seems to be related to PC/SC. Do you have any hints on the >> possible cause ? >> >> ---- >> >> ii libopenct1 0.6.20-1.2 >> ii libpcsc-perl 1.4.12-1build2 >> ii libpcsclite1:amd64 1.8.5-1ubuntu1 >> ii openct 0.6.20-1.2 >> ii opensc 0.12.2-2ubuntu2 >> ii pcsc-tools 1.4.20-1 >> ii pcscd 1.8.5-1ubuntu1 >> ii libccid 1.4.7-1 > > Remove openct and libopenct1 packages. > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com > > > ------------------------------ > > End of Muscle Digest, Vol 107, Issue 5 > ************************************** _______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
