Is there any card reader that supports extended apdu with ccid?
Cheers,
Tomas
[EMAIL PROTECTED] wrote:
Tomas,
You are right. We are handling Extended APDUs in a different way.
There will be surely be 64 bits drivers available in the mid-term
future, but not right now.
Mit freundlichen Grüßen
Best regards,
Thomas Bruendl
Development Manager
OMNIKEY
Ferihumerstrasse 13
A-4040 Linz
Austria
Tel +43 (0) 732 / 602220 - 32
Mobile +43 (0) 664 / 1106386
Fax +43 (0) 732 / 602220 - 15
E-Mail [EMAIL PROTECTED]
Web www.omnikey.com
______________________________________
CARDEXpo, Moscow, September 27-29th, Booth A18
*Tomas Gustavsson <[EMAIL PROTECTED]>*
Gesendet von: [EMAIL PROTECTED]
16-09-05 12:05 PM
Bitte antworten an
MUSCLE <[email protected]>
An
MUSCLE <[email protected]>
Kopie
Thema
Re: [Muscle] ccid driver and extended APDU
According to my collegue Lars you CAN use extended apdu with the OnmiKey
driver
(which is not avilable for 64 bit linux). Perhaps the reader does not
follow
ccid completely, but the driver knows it can handle it.
Cheers,
Tomas
Tomas Gustavsson wrote:
>
> Hi, here is my output from my CardMan 3121, it seems to be the same as
> yours, i.e. it does not report extended apdu.
>
> I'll look into it some more.
>
> Cheers,
> Tomas
>
> ifdhandler.c:998:init_driver LogLevel: 0x0003
> ifdhandler.c:1009:init_driver DriverOptions: 0x0000
> ifdhandler.c:144:IFDHCreateChannel lun: 0
> ccid_usb.c:225:OpenUSBByName Manufacturer: Ludovic Rousseau
> ([EMAIL PROTECTED])
> ccid_usb.c:235:OpenUSBByName ProductString: Generic CCID reader v0.9.3
> ccid_usb.c:241:OpenUSBByName Copyright: This driver is protected by
> terms of the GNU General Public License version 2, or (at your option)
> any later version.
> ccid_usb.c:376:OpenUSBByName Found Vendor/Product: 076B/3021 (CardMan
3121)
> ccid_usb.c:378:OpenUSBByName Using USB bus/device: 001/003
> Parsing Interface Descriptor for device: 001/003
> idVendor: 0x076B
> iManufacturer: OMNIKEY AG
> idProduct: 0x3021
> iProduct: Smart Card Reader USB
> bcdDevice: 0.01 (firmware release?)
> bLength: 9
> bDescriptorType: 4
> bInterfaceNumber: 0
> bAlternateSetting: 0
> bNumEndpoints: 3
> bInterfaceClass: 0x0B [Chip Card Interface Device Class (CCID)]
> bInterfaceSubClass: 0
> bInterfaceProtocol: 0
> iInterface: 0
> CCID Class Descriptor
> bLength: 0x36
> bDescriptorType: 0x21
> bcdCCID: 1.00
> bMaxSlotIndex: 0x00
> bVoltageSupport: 0x07
> 5.0V
> 3.0V
> 1.8V
> dwProtocols: 0x0000 0x0003
> T=0
> T=1
> dwDefaultClock: 4.800 MHz
> dwMaximumClock: 8.000 MHz
> bNumClockSupported: 0x04
> dwDataRate: 10752 bps
> dwMaxDataRate: 412903 bps
> bNumDataRatesSupported: 106
> dwMaxIFSD: 254
> dwSynchProtocols: 0x00000007
> dwMechanical: 0x00000000
> No special characteristics
> dwFeatures: 0x000207B2
> Automatic parameter configuration based on ATR data
> Automatic ICC clock frequency change according to parameters
> Automatic baud rate change according to frequency and Fi, Di
parameters
> Automatic PPS made by the CCID
> CCID can set ICC in clock stop mode
> NAD value other than 00 accepted (T=1)
> Automatic IFSD exchange as first exchange (T=1)
> Short APDU level exchange
> dwMaxCCIDMessageLength: 271 bytes
> bClassGetResponse: 255
> bClassEnveloppe: 255
> wLcdLayout: 0x0000
> bPINSupport: 0x00
> bMaxCCIDBusySlots: 1
>
> Ludovic Rousseau wrote:
>
>> On 14/09/05, Tomas Gustavsson <[EMAIL PROTECTED]> wrote:
>>
>>> Hi again...
>>
>>
>>
>> Hello again :-)
>>
>>
>>> Related to my work on 64-bit systems...
>>> I am using a siemens smart card using 2048 bit RSA keys. This requires
>>> extended apdu, and I notice on your excellent CCID driver homepage,
>>> Ludovic, that "Not yet supported features" includes Extended APDU.
>>>
>>> Do you have a plan when this will be supported?
>>
>>
>>
>> I do not yet have a CCID reader that supports extended APDU AFAIK.
>> According to the CCID specification the reader should indicate his
>> support of extended APDU using the 00040000h bit in dwFeatures (page
>> 19 of [1]).
>>
>>
>>> I am using a CardMan 3121 reader, and Onmikeys proprietary drivers are
>>> not available for 64-bit linux.
>>
>>
>>
>> According to [2] the CardMan 3121 reader does not have the "magic" bit
>> set. Maybe OmniKey has a firmware upgrade.
>>
>> Can you run the ccid/src/parse command on your CardMan 3121 reader and
>> send me the result?
>>
>> Bye,
>>
>> [1]
>>
http://www.usb.org/developers/devclass_docs/DWG_Smart-Card_CCID_Rev110.pdf
>>
>> [2]
>>
http://svn.debian.org/wsvn/pcsclite/trunk/Drivers/ccid/readers/CardMan3121.txt?op=file&rev=0&sc=0
>>
>>
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
------------------------------------------------------------------------
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
