You can subscribe to this list here.
2002 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(12) |
May
(18) |
Jun
(53) |
Jul
(95) |
Aug
(59) |
Sep
(35) |
Oct
(79) |
Nov
(80) |
Dec
(50) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(89) |
Feb
(80) |
Mar
(120) |
Apr
(110) |
May
(98) |
Jun
(127) |
Jul
(75) |
Aug
(67) |
Sep
(71) |
Oct
(90) |
Nov
(64) |
Dec
(59) |
2004 |
Jan
(62) |
Feb
(71) |
Mar
(76) |
Apr
(69) |
May
(47) |
Jun
(56) |
Jul
(31) |
Aug
(70) |
Sep
(36) |
Oct
(48) |
Nov
(24) |
Dec
(38) |
2005 |
Jan
(25) |
Feb
(34) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(48) |
Jul
(21) |
Aug
(14) |
Sep
(16) |
Oct
(22) |
Nov
(3) |
Dec
(10) |
2006 |
Jan
(28) |
Feb
(46) |
Mar
(30) |
Apr
(27) |
May
(27) |
Jun
(18) |
Jul
(47) |
Aug
(29) |
Sep
(24) |
Oct
(42) |
Nov
(8) |
Dec
(3) |
2007 |
Jan
(22) |
Feb
(9) |
Mar
(22) |
Apr
(34) |
May
(21) |
Jun
(6) |
Jul
(16) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(8) |
Dec
(4) |
2008 |
Jan
(11) |
Feb
(10) |
Mar
(25) |
Apr
(8) |
May
(22) |
Jun
(8) |
Jul
(6) |
Aug
(7) |
Sep
(1) |
Oct
(9) |
Nov
(14) |
Dec
(14) |
2009 |
Jan
(32) |
Feb
(11) |
Mar
(14) |
Apr
(4) |
May
(17) |
Jun
(8) |
Jul
(3) |
Aug
(19) |
Sep
(15) |
Oct
(13) |
Nov
(13) |
Dec
(16) |
2010 |
Jan
(11) |
Feb
(22) |
Mar
(28) |
Apr
(9) |
May
(11) |
Jun
(13) |
Jul
(16) |
Aug
(5) |
Sep
(4) |
Oct
(6) |
Nov
|
Dec
(4) |
2011 |
Jan
(7) |
Feb
(10) |
Mar
(14) |
Apr
(19) |
May
(17) |
Jun
(7) |
Jul
(21) |
Aug
(8) |
Sep
(7) |
Oct
(6) |
Nov
(11) |
Dec
(4) |
2012 |
Jan
(5) |
Feb
(7) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(12) |
Jul
(5) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(14) |
Sep
(18) |
Oct
(1) |
Nov
(6) |
Dec
(3) |
2014 |
Jan
(3) |
Feb
(5) |
Mar
(9) |
Apr
(1) |
May
(18) |
Jun
(12) |
Jul
(3) |
Aug
(8) |
Sep
(8) |
Oct
(3) |
Nov
(3) |
Dec
|
2015 |
Jan
|
Feb
(4) |
Mar
(6) |
Apr
(3) |
May
|
Jun
(2) |
Jul
(4) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Martin O. <mar...@gm...> - 2015-08-20 08:28:19
|
Hello, using the current rdesktop 1.8.3, we experience problems when connection to a load balanced RDP cluster (Windows Server 2008 R2). The login is working successfully when no redirection happens, i.e. the DNS round robin returns the IP of the server where the current session is active. When rdesktop displays the message that the connection is redirected, the user is thrown back to the login screen: $ rdesktop server Autoselected keyboard map de [...] Connection established using SSL. Redirected to user@serverip session -631381426. -> back to login screen The behaviour is the same with password and smartcard login. Is this a known problem? Kind regards, Martin Oehler |
From: Henrik A. <hen...@ce...> - 2015-08-20 08:07:39
|
Greetings rdesktop community. The rdesktop project is now moved to GitHub. This means that the hosted project services on SourceForge; www.rdesktop.org, svn repositories, issue trackers and mailing lists has found a new home and will be locked down. - A new static project page with updated information has been created. It is hosted by github.io, you find it here [1]. - The subversion repository has been migrated and is available at rdesktop organization page at GitHub [2]. - A BountySource rdesktop team [3] is created for donations and the ability to create bounties for issues. - New mailing lists are created and hosted by Google groups, read how to subscribe and use the new lists at the Community section on the new homepage [1]. [1] http://www.rdesktop.org [2] http://github.com/rdesktop Best Regards, rdesktop team |
From: Elfi H. <EH...@in...> - 2015-08-10 11:03:59
|
The changes from revisions 1595, 1597, 1598 don't work with the ccid driver from the pcsc-lite project. This driver uses control codes that overlap with the 49 << 16 used in Windows codes. In the output of GET_FEATURE_REQUEST these codes are translated to the Windows format. Then when using one of those codes, translation in the other direction is not done because the condition "(dwControlCode & 0xffff0000) == (49 << 16)" always results to false. This might be fixed be adjusting the mask, but my opinion is that control codes returned by the reader driver should always be left alone, because only this way we can be sure that the driver will understand the codes sent back to it. Translating makes assumptions about the used bits that might not be valid. |
From: Stephan S. <ss...@gm...> - 2015-08-06 05:04:14
|
Hi all, I'm having the same problem as described already in 2003 (see here http://sourceforge.net/p/rdesktop/mailman/message/6643699/) which is that I get wrong colors (i.e. brown instead of blue). According to the old mailings this would have to be solved by fixing xwin.c. Was this ever done? Best regards, Stephan |
From: <mcg...@ma...> - 2015-07-10 09:31:15
|
Hi, I would like to use a bepo keyboard layout. I read that a patch has been submitted and included in 2010. The problem might be me but I can't seem to use it: ERROR: Failed to open keymap fr-bepo I have rdesktop-1.8.3-r1 on Parabola. I have looked at the keymaps folder on sourceforge but the layout isn't there. There's a link in the original patch request, but it leads nowhere. Has it been removed? If it's not recoverable, I can try to (re)create it. I have 2 obstacles: * scancodes: Not all the keys are found in scancodes.h, for instance accented characters. * keysym-names: The keymapping.txt file says it's found in the error message but it isn't clear for me which one. xmodmap -pke returns a list of what looks like scancodes and keysyms. From messages on the mailing list, I understand that keysyms are read on the local system, so they could come from this command. But what about the scancodes for accented characters, special quotes, etc? Thanks in advance for any hint! -- McGregor |
From: Henrik A. <hen...@ce...> - 2015-07-03 11:13:10
|
Hi everyone, We are considering to move away from SF to github before October 2015. Currently we are working to migrate svn commits, tags and branches into git. We need to map commit authors from svn to git with additional full names and email addresses. I have done some investigation and came up with the following mapping table: astrand = Peter Åstrand <as...@ce...> hean01 = Henrik Andersson <he...@ce...> ossman_ = Pierre Ossman <os...@ce...> forsberg = Erik Forsberg <for...@ce...> jdmeijer = Jeroen Meijer <je...@ol...> jsorg71 = Jay Sorg <j...@am....x> matthewc = Matt Chapman <mat...@cs...> matty = Matt Chapman <mat...@cs...> mmihalik = Michal Mihalik <mmh...@sm...> n-ki = Peter Kallden <pet...@ub...> stargo = Michael Gernoth <mi...@ge...> This table will be used AS presented here, and you who wants to use another email address then the one above reply to this email with updated information before end of August 2015. Kind Regards Henrik Andersson |
From: Christopher R. <cj...@tr...> - 2015-07-03 09:54:58
|
I can't find SeamlessRDP server on the internet. Is it changed and can't be used now? If it is. Is there another way to access remote app? Yes, it doesn't seem quite so obvious. See https://www.cendio.com/seamlessrdp at the bottom of the page it states: Get the server side component, "seamlessrdpshell". Pre-built binaries are included in the ThinLinc WTS Tools package, which is part of the ThinLinc Server Bundle. In general, ThinLinc is a proprietary product which requires licenses, but the SeamlessRDP components are Open Source and can be used for free. The "seamlessrdpshell" is installed in "%ProgramFiles%\ThinLinc\WTSTools". I would download the ThinLinc server and hopefully you will find the WTS Tools within it, and hopefully seamlessrdpshell. Chris Roberts |
From: 小红手 <dre...@12...> - 2015-07-03 05:01:16
|
Hi I can't find SeamlessRDP server on the internet. Is it changed and can't be used now? If it is. Is there another way to access remote app? |
From: Chris C. <xr...@xr...> - 2015-06-27 02:45:44
|
Even if there’s not an rdesktop switchy way to do this, it might be pretty easy to wrap rdesktop in a script to check the cert and pop an error if the cert fails, using openssl, you could do something like: openssl s_client -connect $1:3389 Then search for verify return or something else we can believe to make sure the cert is valid, then you throw an “are you sure" dialog if it doesn’t pass the test? > On Jun 26, 2015, at 12:25 , Julian J. M. <jul...@gm...> wrote: > > Hi, > > I'm using rdesktop with SSL enabled RDP servers, some with self-signed and some with purchased thirdparty certificates. > > The windows TS client warns when connecting to a server with a self-signed cert, but rdesktop makes absolutely no difference, which makes it less secure, as you could be subject to a MitM without noticing it. > > Is there any way to force the verification of the server certificate and that it matches the host name? > > I'm using version 1.8.3: > $ rdesktop server.host > ERROR: Failed to open keymap en-us > ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized ? > Connection established using SSL. > WARNING: Remote desktop does not support colour depth 24; falling back to 16 > > Thanks, > Julian. > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o_______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users |
From: Julian J. M. <jul...@gm...> - 2015-06-26 16:25:59
|
Hi, I'm using rdesktop with SSL enabled RDP servers, some with self-signed and some with purchased thirdparty certificates. The windows TS client warns when connecting to a server with a self-signed cert, but rdesktop makes absolutely no difference, which makes it less secure, as you could be subject to a MitM without noticing it. Is there any way to force the verification of the server certificate and that it matches the host name? I'm using version 1.8.3: $ rdesktop server.host ERROR: Failed to open keymap en-us ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized ? Connection established using SSL. WARNING: Remote desktop does not support colour depth 24; falling back to 16 Thanks, Julian. |
From: Mican J. <Jin...@lg...> - 2015-04-08 17:20:12
|
Hello, well, it is taking bit longer than expected with Cryptovision, I am still waiting for trial to even test it. Have someone solved similar situation in another way? Thanks Henry Von: Mican Jindrich [mailto:Jin...@lg...] Gesendet: Freitag, 27. März 2015 09:34 An: Robin Jonsson; rde...@li... Betreff: Re: [rdesktop-users] Card attributes gets lost through RDP session with rdesktop Hello Robin, thank you very much for your reply! I am happy that someone finally gave me somewhere to look while I have already checked tens if not over hundred Google search result... (I am pro in Windows servers, their server apps etc, but linux-windows communication is kind of new to me) I will try it out and will let know if it will work. Sadly even when it will work, I have to find solution which won't require high investments... and I am not sure about prices of Cryptovision. Thank you again! Henry Von: Robin Jonsson [mailto:Rob...@en...] Gesendet: Freitag, 27. März 2015 09:18 An: Mican Jindrich; rde...@li...<mailto:rde...@li...> Betreff: Re: [rdesktop-users] Card attributes gets lost through RDP session with rdesktop 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... |
From: Mican J. <Jin...@lg...> - 2015-04-08 05:56:48
|
Hi Alexandre, is there anything specific about those computer or RDP hosts? Or maybe you have an application there as a service that might collide in some sort of way with RDP session. I was using both 1.7.1 and 1.8.3 but I never had problems with freezing, I was using it with both fat and thin clients. Henry -----Ursprüngliche Nachricht----- Von: Alexandre Magnat [mailto:ale...@me...] Gesendet: Dienstag, 07. April 2015 11:08 An: rde...@li... Betreff: [rdesktop-users] Random rdesktop freeze and kernel panic Hi, We use rdesktop 1.8.3 in a live distribution (LTSP) on thin client. Some users have randomly a freeze of their rdp session and it's result on a kernel panic. A user has tried for example to modify a PowerPoint from a Windows Session on his thin client. The rdesktop program has freezed when the user has begin to modify the PowerPoint. The thin client has been rebooted. This strace was logged with the 1.7.1. For the moment, I haven't log for the 1.8.3 version but the problem seem to be the same... recvmsg(4, 0xbfc73154, 0) = -1 EAGAIN (Resource temporarily unavailable) select(6, [4 5], [], NULL, {60, 0}) = 1 (in [5], left {59, 999991}) gettimeofday({1427207735, 661807}, NULL) = 0 recv(5, "\2\360\200h\0\1\3\353p&\10\0\0\0|Nv\317:c\332M:E\233\257\260\3f|\211\r"..., 48, 0) = 48 poll([{fd=4, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=4, revents=POLLOUT}]) writev(4, [{"h\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4 recvmsg(4, 0xbfc73154, 0) = -1 EAGAIN (Resource temporarily unavailable) select(6, [4 5], [], NULL, {60, 0}^CProcess 5167 detached <detached ...> Have you an idea or anybody have got the same problem ? ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ rdesktop-users mailing list rde...@li... https://lists.sourceforge.net/lists/listinfo/rdesktop-users |
From: Alexandre M. <ale...@me...> - 2015-04-07 09:26:32
|
Hi, We use rdesktop 1.8.3 in a live distribution (LTSP) on thin client. Some users have randomly a freeze of their rdp session and it's result on a kernel panic. A user has tried for example to modify a PowerPoint from a Windows Session on his thin client. The rdesktop program has freezed when the user has begin to modify the PowerPoint. The thin client has been rebooted. This strace was logged with the 1.7.1. For the moment, I haven't log for the 1.8.3 version but the problem seem to be the same... recvmsg(4, 0xbfc73154, 0) = -1 EAGAIN (Resource temporarily unavailable) select(6, [4 5], [], NULL, {60, 0}) = 1 (in [5], left {59, 999991}) gettimeofday({1427207735, 661807}, NULL) = 0 recv(5, "\2\360\200h\0\1\3\353p&\10\0\0\0|Nv\317:c\332M:E\233\257\260\3f|\211\r"..., 48, 0) = 48 poll([{fd=4, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=4, revents=POLLOUT}]) writev(4, [{"h\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4 recvmsg(4, 0xbfc73154, 0) = -1 EAGAIN (Resource temporarily unavailable) select(6, [4 5], [], NULL, {60, 0}^CProcess 5167 detached <detached ...> Have you an idea or anybody have got the same problem ? |
From: Mican J. <Jin...@lg...> - 2015-03-27 08:34:28
|
Hello Robin, thank you very much for your reply! I am happy that someone finally gave me somewhere to look while I have already checked tens if not over hundred Google search result... (I am pro in Windows servers, their server apps etc, but linux-windows communication is kind of new to me) I will try it out and will let know if it will work. Sadly even when it will work, I have to find solution which won't require high investments... and I am not sure about prices of Cryptovision. Thank you again! Henry Von: Robin Jonsson [mailto:Rob...@en...] Gesendet: Freitag, 27. März 2015 09:18 An: Mican Jindrich; rde...@li... Betreff: Re: [rdesktop-users] Card attributes gets lost through RDP session with rdesktop 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... |
From: Robin J. <Rob...@en...> - 2015-03-27 08:31:08
|
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… |
From: Mican J. <Jin...@lg...> - 2015-03-27 07:42:33
|
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... |
From: <ste...@bt...> - 2015-03-12 14:50:15
|
> -----Original Message----- > From: Sean M. Pappalardo [mailto:spa...@re...] > Sent: 12 March 2015 14:22 > To: Hindmarch,SJ,Stephen,TNV82 R; rde...@li... > Subject: Re: [rdesktop-users] No password prompt when connecting to Windows > 8.1 > > > > On 03/12/2015 04:39 AM, ste...@bt... wrote: > > I have now been upgraded to a new Windows 8.1 laptop and now I cannot > > login. The rdesktop session opens and I can see the MS account I want to > > log into, but when I select it there is no password box for me to > > authenticate into the account with. I have tried passing the password in > > the command line with the "-p" option but this has no effect. > > The default system policy on newer Windows versions allows only > Network-Level Authentication (where the RDP client does the > authentication via Kerberos before actually showing the remote screen.) > > Take a look under Control Panel -> System, Advanced properties, Remote > tab. You may need to choose to "Allow connections from computers running > any version of Remote Desktop" Sean, Thank you for your response. I have looked and the box that says "Only allow connections ... with Network Level Authentication" is unticked but that whole section of the control panel is greyed out. Do you think it might be controlled by a central policy? I am logged in as a user with administrator access. There is no option as you describe it. ... Actually I have cracked it. With a bit of lateral thinking I clicked in the panel for others to log in instead of the one for myself. Then I could enter my domain, username and password and gain access. Thanks anyway for listening to me and I hope this solves the problem for somebody else. > > Sincerely, > Sean M. Pappalardo > Sr. Networks Engineer > Renegade Technologies |
From: Sean M. P. <spa...@re...> - 2015-03-12 14:40:40
|
On 03/12/2015 04:39 AM, ste...@bt... wrote: > I have now been upgraded to a new Windows 8.1 laptop and now I cannot > login. The rdesktop session opens and I can see the MS account I want to > log into, but when I select it there is no password box for me to > authenticate into the account with. I have tried passing the password in > the command line with the “-p” option but this has no effect. The default system policy on newer Windows versions allows only Network-Level Authentication (where the RDP client does the authentication via Kerberos before actually showing the remote screen.) Take a look under Control Panel -> System, Advanced properties, Remote tab. You may need to choose to "Allow connections from computers running any version of Remote Desktop" Sincerely, Sean M. Pappalardo Sr. Networks Engineer Renegade Technologies |
From: <ste...@bt...> - 2015-03-12 11:51:49
|
My company makes me use a Windows laptop for email, IM and a few application that need an MS O/S. I use an rdesktop session from my Fedora Core 20 workstation to keep the laptop screen on one of my virtual desktops. This has been working fine with rdesktop 1.8.3 and windows 7. I have now been upgraded to a new Windows 8.1 laptop and now I cannot login. The rdesktop session opens and I can see the MS account I want to log into, but when I select it there is no password box for me to authenticate into the account with. I have tried passing the password in the command line with the "-p" option but this has no effect. Has anybody seen this before. I have a feeling that it might be a security policy thing but my local support people are clueless as they do not support linux. I can start a MS Remote Desktop session from my old laptop to the new and that does allow me to authenticate, so it is something peculiar to the session initiated by rdesktop. The command line I am using is rdesktop -u <username> -d <domain> -k en-gb -g 1900x1000 -a 16 <ip_address> Any help would be appreciated. Steve Hindmarch |
From: Øyvind 'b. H. <bo...@dh...> - 2015-02-26 20:21:50
|
I'm curious how you prevent the user from simply disconnecting. Like, clicking on the desktop and doing alt+f4 and such. On 26/02/15 20:23, Peter Astrand wrote: > > It's in the code, xkeymap.c: > > case XK_Return: > if ((get_key_state(state, XK_Alt_L) || get_key_state(state, XK_Alt_R)) > && (get_key_state(state, XK_Control_L) > || get_key_state(state, XK_Control_R))) > { > /* Ctrl-Alt-Enter: toggle full screen */ > if (pressed) > xwin_toggle_fullscreen(); > return True; > } > break; > > Br, > Peter > > On Thu, 26 Feb 2015, Neil Underwood wrote: > >> I'd like to use rdesktop as part of a simple thin client set up on a >> Raspberry Pi for 3 kiosks in the lobby at my office. My biggest concern >> is the ability to toggle out of full screen mode with Ctrl-Alt-Enter. >> Is this something that is managed through keymapping within rdesktop or >> is this handled by the WM/DE? I didn't see anything obvious when >> browsing the rdesktop code. >> >> I realize an alternative would be to strip down the underlying desktop >> and adjust permissions to basically not allow anything but rdesktop to >> be running, but this would be a much more elegant solution to avoid >> leaving full screen to begin with. >> >> Thanks >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for all >> things parallel software development, from weekly thought leadership blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> rdesktop-users mailing list >> rde...@li... >> https://lists.sourceforge.net/lists/listinfo/rdesktop-users >> > > > --- > Peter Astrand ThinLinc Chief Developer > Cendio AB https://cendio.com > Teknikringen 8 https://twitter.com/ThinLinc > 583 30 Linkoping https://facebook.com/ThinLinc > Phone: +46-13-214600 https://google.com/+CendioThinLinc > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |
From: Peter A. <as...@ce...> - 2015-02-26 19:41:28
|
It's in the code, xkeymap.c: case XK_Return: if ((get_key_state(state, XK_Alt_L) || get_key_state(state, XK_Alt_R)) && (get_key_state(state, XK_Control_L) || get_key_state(state, XK_Control_R))) { /* Ctrl-Alt-Enter: toggle full screen */ if (pressed) xwin_toggle_fullscreen(); return True; } break; Br, Peter On Thu, 26 Feb 2015, Neil Underwood wrote: > I'd like to use rdesktop as part of a simple thin client set up on a > Raspberry Pi for 3 kiosks in the lobby at my office. My biggest concern > is the ability to toggle out of full screen mode with Ctrl-Alt-Enter. > Is this something that is managed through keymapping within rdesktop or > is this handled by the WM/DE? I didn't see anything obvious when > browsing the rdesktop code. > > I realize an alternative would be to strip down the underlying desktop > and adjust permissions to basically not allow anything but rdesktop to > be running, but this would be a much more elegant solution to avoid > leaving full screen to begin with. > > Thanks > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > --- Peter Astrand ThinLinc Chief Developer Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linkoping https://facebook.com/ThinLinc Phone: +46-13-214600 https://google.com/+CendioThinLinc |
From: Neil U. <Ne...@su...> - 2015-02-26 17:05:15
|
I'd like to use rdesktop as part of a simple thin client set up on a Raspberry Pi for 3 kiosks in the lobby at my office. My biggest concern is the ability to toggle out of full screen mode with Ctrl-Alt-Enter. Is this something that is managed through keymapping within rdesktop or is this handled by the WM/DE? I didn't see anything obvious when browsing the rdesktop code. I realize an alternative would be to strip down the underlying desktop and adjust permissions to basically not allow anything but rdesktop to be running, but this would be a much more elegant solution to avoid leaving full screen to begin with. Thanks |
From: Patrick <jok...@gm...> - 2015-02-12 15:48:24
|
Hello, since the update to 1.8.3 we have the problem that printing is really slow (eg 2page PDF, 100kb, grows up to 70-100MB in the windows spooler, it takes hour to print...). so i checked it out and saw that the "ms publisher" driver is used and not the defined "Apple Laserwriter 12/640". The machines we connect are windows xp sp3. when i connect to our 2012 RDS Server the right driver ("apple laserwriter..") is used. is this a know bug? thats our rdesktop command: rdesktop -r clipboard:PRIMARYCLIPBOARD -r printer:localprintername="Apple LaserWriter 12/640 PS" -a 15 -z -x m -P -b -g 1280x1024 servername thanks for any help! patrick -- "Ungeschehene Tatsachen können einen katastrophalen Mangel an Folgen auslösen." |
From: Henrik A. <hen...@ce...> - 2014-11-11 10:25:07
|
> Can anyone help me fixing this? If this is a bug where should I file > it and what is needed? If this behaviour correlates with kernel ASLR, > this should be easily reprducible. Anyway any suggestions or > questions are appreciated. Thank you in advance > I could not reproduce having ASLR enabled, could you provide a backtrace with debug symbols for this SIGSEGV ? Regards, Henrik Andersson |
From: Stückenschneider, B. <bjo...@bu...> - 2014-11-10 16:29:51
|
Hi, I just stumpled on a seg fault while trying to use rdesktop after an update of my pc. I run gentoo 3.16.5 x86_64 and use rdesktop-1.8.3 Log file tells me something like: [ 8221.014342] rdesktop[4670]: segfault at 0 ip 00007feb1deb5b67 sp 00007fff8d069888 error 6 in libc-2.19.so[7feb1de2a000+19d000] [ 8234.595630] rdesktop[4672]: segfault at 0 ip 00007f09df10eb67 sp 00007fff91346278 error 6 in libc-2.19.so[7f09df083000+19d000] [striped unrelated log entries] [10909.885587] rdesktop[26919]: segfault at 0 ip 00007f37cfbf3b67 sp 00007fffc4f79828 error 6 in libc-2.19.so[7f37cfb68000+19d000] [12137.604414] rdesktop[30355]: segfault at 0 ip 00007f8347f7bb67 sp 00007fff12265688 error 6 in libc-2.19.so[7f8347ef0000+19d000] [striped unrelated log entries] [12197.597852] rdesktop[30370]: segfault at 0 ip 00007ff44ea30b67 sp 00007ffffc4c5748 error 6 in libc-2.19.so[7ff44e9a5000+19d000] [12233.678555] rdesktop[30375]: segfault at 0 ip 00007f05f23adb67 sp 00007fff8562ef68 error 6 in libc-2.19.so[7f05f2322000+19d000] [12238.834934] rdesktop[30376]: segfault at 0 ip 00007fc0942ffb67 sp 00007fff15a5e7c8 error 6 in libc-2.19.so[7fc094274000+19d000] This happens with my user and root. As soon as I set 'echo '0' >> /proc/sys/kernel/randomize_va_space' it is possible to start it as root. I activated ASLR in kernel space with this update, so this makes sense to me. Anyway this looks like a bug to me but maybe someone proves me wrong. Can anyone help me fixing this? If this is a bug where should I file it and what is needed? If this behaviour correlates with kernel ASLR, this should be easily reprducible. Anyway any suggestions or questions are appreciated. Thank you in advance Bjoern Stueckenschneider |