[ rdesktop-Bugs-2777237 ] rdesktop with smartcard

Bugs item #2777237, was opened at 2009-04-21 14:32
Message generated for change (Comment added) made by rahulravindran
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=2777237&group_id=24366

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Authentication
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: rahulkr (rahulravindran)
Assigned to: Nobody/Anonymous (nobody)
Summary: rdesktop with smartcard

Initial Comment:
i have installed rdesktop 1.6 which has smart card option in linux OS.i plugin the usb smart card reader
and started pcscd deamon then i invoke the rdesktop with scard option the rdesktop recognized the
smart card which is inserted in the smart card reader.But problem is when i unplug the smart card and plug it again (while rdesktop still running) then rdesktop does not recognized the smart card.
Please help me.I have no clue what is happening but this procedure work perfectly with windows

----------------------------------------------------------------------

Comment By: rahulkr (rahulravindran)
Date: 2009-07-01 10:48

Message:
Actually real problem i had with aladdin etoken 72 pro java - smartcard.I
was able to solve the plugin-plugout issue by controlling the behaviour of
the thread i.e with help of udev rules.But it is not consistent.I added
some code in the TS_SCARDGETCHANGE() function to work this issue but it is
not perfect.Now u says that this virtual channel has a problem.What is this
virtual channel?How communication happen on this channel?.Because I explore
various files related to rdesktop but fail to get the problem source.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-06-30 19:57

Message:
I continue my search.  The update of pcsc-lite avoid a segmentation fault
and seems to be a little more stable but sometime (inpredictable...).

I'm looking now at the filesystem virtual channel used from smartcard
messages transmission.  Is it possible that ad problems (and the deadlock
in scard.c) come from there?  The filesystem virtual channel is implemented
in rdpdr.c (the channel is called rdpdr).

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-06-25 18:41

Message:
As said in an other post on this mailing list, the upgrade of pcsclite
help.  I have updated pcsc-lite to version 1.5.4 (the latest one) and now
the hotplug works with AD but for a limited numbers of times...

The problems seems to be on the pcscd side.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-06-25 15:58

Message:
Uncommenting the block of code managing the hotplug allow the smart-card to
works perfectly with a MS Windows   that is not inside a MS domain.  

I start trying to debug with a MS Windows machine inside a domain and
found that the problem come from a deadlock in thread_function.  The
smart-card thread is locked on pthread_cond_wait without being waked up. 
The problem is not reproducible with MSTSC.EXE on MS Windows.  Certainly a
bug somewhere in rdesktop but why AD integration has an impact on rdesktop?
 Didn't understand up to now.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-06-23 20:34

Message:
I whish to add some extra information.

We had the same problem and we have discovered an interaction with MS
Active Directory.  When the windows machine on which we want to connect is
outside any domain, redirection and insert/eject events works perfectly. 
When the machine is added to the domain, we have the same problem.

The problem occurs with out-of-the box policies on Windows 2003 and
Windows 2008 server with the default policies.  And I have found no policy
directly inpacting RDP in these default policies.  So, up-to-now I have no
extra-idea or workaround.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-05-31 01:36

Message:
there is some code in the scard.c which enables the "hotplug" feature, it's
disabled, but when i enabled i was able to hotplug the card in the reader,
i'm just not sure if it is buggy...

----------------------------------------------------------------------

Comment By: rahulkr (rahulravindran)
Date: 2009-04-23 18:18

Message:
Is there any patch for this ?

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-04-23 18:15

Message:
Is there any patch ready for this problem?

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-04-21 18:48

Message:
You haven't done anything wrong. There is a bug in rdesktop. The set of
users using both rdesktop and smart cards is growing but still small; the
subset of those users who can hack on the smartcard support is even
smaller. So bugs in this area are not fixed very quickly.

The workaround is to set your terminal server to not log people off as
soon as they disconnect. Then when you remove the smartcard (for whatever
reason), you can disconnect without logging out of Windows by closing the
rdesktop client, and restart rdesktop with the smart card inserted, to
reconnect to the terminal server. Then you'll start your Windows session
where you left it off, with the smartcard working.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=2777237&group_id=24366

------------------------------------------------------------------------------