Re: access to SmartTerminal XX44

2014-03-20 15:05 GMT+01:00 Vieri <[email protected]>:
> Hi,

Hello,

> I'm having trouble accessing a smartcard (authentic driver - Cherry MY 8040 USB multiboard keyboard & reader).
>
> pcsc_scan seems to see and identify the card correctly.
>
> However,
> I haven't tried anything else in Linux (like use the certificate within
> the card to sign something or access a web site, etc.). In fact,
> all I really want is to "redirect" the smartcard data to a Windows 2003 Terminal Server.
> I use the following command from a Linux client:
>
> rdesktop -r scard rdpserver
>
> I even tried to set the device names accordingly:
>
> rdesktop -r scard:"Cherry GmbH SmartTerminal XX44 00 00"="Cherry GmbH SmartTerminal XX44 0" -f "$RDP_SERVER"
>
> I
> can see that the reader is detected in Windows Terminal Server and that
> it detects the events of inserting and removing a card.
> However,
> when connecting with a Windows client, a user certificate is
> automatically installed in several apps (IE, etc.) whereas it's not if I
> connect with a Linux rdesktop client.
>
> I compared the 2 logs I
> get in the Windows 2003 Terminal Server (PC/SC diagnostics tool) when
> connecting with a Windows client and a Linux rdesktop client.
> Basically,
> when connected from Linux I get "Clock rate" and "BWT" errors. When
> connected from Windows Clock rate=4MHz and BWT=1439.48 work etu
> (actually these 2 values may vary if I connect from other Windows
> clients).
>
> Here are the details (when connected with a Linux client):
> Cherry GmbH SmartTerminal XX44 00 00:
>
> Attribute              |Value
> --------------------------------+----------------------------------------------
> ATR            |3b fb 18 00 00 81 31 fe 45 00 31 c0 64 77 e9 10 00 01 90 00 62
> Clock rate (MHz)      |Error
> Convention         |direct
> Protocol         |T=1
> (TA1) Divider F         |372
> (TA1) Transfer factor D      |12
> (TB1) VPP supply      |unnecessary
> (TC1) Extra guardtime N      |0 work etu
> (TC2) Work waiting time      |115200 work etu
> (TA3) IFSC (byte)      |254
> (TB3) CWT         |43 work etu
> (TB3) BWT         |Error
> Historical Characters (text)   | 1Àdwé
> Historical Characters (hex)   |00 31 c0 64 77 e9 10 00 01 90 00
>
> I posted more debug information on the following forum:
> http://forums.gentoo.org/viewtopic-t-986680.html

I don't see any problem in the smart card side on GNU/Linux.

rdesktop is also working a minimum since you can get the ATR of the
card on the Windows side. Good.

Windows can't display the "Clock rate" and "BWT" because the Windows
diagnostic tool uses SCardGetAttrib() with the attribute
SCARD_ATTR_CURRENT_CLK (tag: 0x80202) that are is supported by the
PC/SC on the GNU/Linux side.

Maybe your Minidriver, or whatever code is running on the Windows side
to support your card, is also confused by unsupported attributes for
SCardGetAttrib().

Can you debug/modify the Windows code?

Bye

-- 
 Dr. Ludovic Rousseau

_______________________________________________
Muscle mailing list
[email protected]
http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com