Re: [rdesktop-users] Card attributes gets lost through RDP session with rdesktop

[Robin J. <Rob...@en...>]

Hello Henry,

I had somewhat of the same issue.

I had a setup of an IGEL Thin Client with an OmniKey 3121 reader from which I connected via rDesktop to a Windows 7 x64 Client. The card and the reader showed up in Windows and seemed fine until I actually tried to read something. I just got a single flash on the LED and then the software reading hung (certificate export in certmgr.msc or whatever) until the card was removed. Connecting the reader directly to the Windows 7 x64 worked perfectly. So did Windows 7 x64 -> Windows 7 x64 SC RDP redirect. So the issue was Linux + PC/SC + rdesktop + M$ compatibility related.

Installing Cryptovison sc/interface 6.1.6 on Windows solved my issue.

I had some help from Ludovico Rousseau, the main developer of the PC/SC daemon, troubleshooting the rDesktop -> PC/SC hook chain, which turned out to be fine. Cryptovision was very accommodating regarding Trial licenses.

Cheers,
Robin

Från: Mican Jindrich <Jin...@lg...<mailto:Jin...@lg...>>
Datum: 2015March27Friday 08:42
Till: "rde...@li...<mailto:rde...@li...>" <rde...@li...<mailto:rde...@li...>>
Ämne: [rdesktop-users] Card attributes gets lost through RDP session with rdesktop

Hello,

I know that this is just slightly related topic to rdesktop – it might be problem with it or even pcsc, still due to having no idea what to do next, I am writing even here to ask if they do not know solution or did not have similar experience:

I am using openthinclient to get mini-image on thinclients which then connect through RDP to Windows platform. Connector is rdesktop, provider of smartcard drivers – REINER driver + PCSC-Lite.
I have moved onward with everything… made rdesktop 1.8.3 and pscs-lite 1.8.13 for my dev-site but it seems that it did not work as I have expected. (packages for TCO are remade DEB packages – just for info)

But I have problems with Smartcard reader from REINER SCT – Cyberjack e-com plus which does not simply work even with its own drivers, that are provided on web-site. I was trying older rdesktop aswell as the new one I have made, same for pcsc-lite including latest drivers from Reiner…

RDP destination is Windows 2008 R2 SP1 with Reiner SCT SW installed.

On mini client everything works as expected, remote desktop works, USB support works, but when I do test of card reader then everything is fine, but I do not see attributes of card in card reader. On thin-client pcscd does see the card and reader.. pcsc_scan confirms that everything works as expected, but on server side … attributes of card gets lost (reader itself shows just fine, SW reacts on card being in reader or not).

So, it looks like smartcard redirection gets somewhere wrong, I can send screenshots with one of testing applications being not able to receive card attributes, meaning – smartcard redirection goes wrong. I noticed the difference with WTS (Windows RDP system) that share there still refers to smartcard as USB device, while with rdesktop (or even FreeRDP) smartcard is being refered as PC/SC device only (or at least mostly).

Anyone has such an experience? It looks like compatibility issue or so. This is really point where cannot do anything else than check source codes for anything (which I am already doing… but I am getting nowhere)

Thank you very much in advance for any help.

Jindrich Mican alias “Henry”

PS: I have tried this even with laptop with Broadcom cardreader and it was the same, I tried Ubuntu 14.04 (64bit)/Debian 7.8 (32bit).. I tried old rdesktop, new, old drivers and new etc. Well, most of things that you could think of, even 3 different applications on host side to check smartcard reader…