Live data from Hacker News

Xrdp: An open source RDP server

github.com

31–40 of 80 posts

Re: Xrdp: An open source RDP server

#32

Earlier quoted context omitted.

>long tutorials with config files and services On the server: x11vnc -display :0 -noxdamage -shared -repeat -forever On the client: ssh -T server 'nc 127.0.0.1 5900' vncviewer 127.0.0.1:5900

ssh -N -L5900:127.0.0.1:5900 user@server is usually cleaner than using nc, it doesn't require running any commands on the remote system and lets you do any port changing that you need to make things work between each side.

Right, I had to use `nc` instead of forwarding the port from SSH itself because I use systemd socket activation for that ssh command, with

    ExecStart=ssh -T server 'nc 127.0.0.1 5900'
    StandardInput=socket
    StandardOutput=socket
in the service file and

    ListenStream=0.0.0.0:5900
in the socket file.

The socket has to be connected to stdin/stdout instead of using SSH forwarding since SSH doesn't support fd-based socket activation.

Re: Xrdp: An open source RDP server

#33

I use RDP multiple times every day. I have tested Linux RDP server implementations and they are very buggy and really not production ready only NX kinda is (yet not as good as MS RDP). VNC is so bad and lacks so many features that it's not even considered a competition - it's old insecure slow protocol that should be forgotten by now.

RDP isn't really meant to be cross platform, right? It's a Windows graphics server telling a Windows client how to draw some Windows widgets. The fact that there are working Linux implementations at all is impressive. By contrast, VNC is pretty close to just sending an image of the screen, with some clever optimization.

VNC over SSH should be as secure as you need, but it's never likely to be as performant as RDP.

Re: Xrdp: An open source RDP server

#34
post #27

I used to maintain some linux remote desktops at my job for specific workflows of certain employees. Wow, using xrdp was a complete gong show to manage. The most common bugs were in the assignment of displays on user logon, as well as a crappy, often buggy, login screen (though GUI logins for linux are fascinatingly weird pretty much universally.) That being said, even in evaluating alternatives there wasn't anything…

> That being said, even in evaluating alternatives there wasn't anything much better.

Do you remember what issues were there with NX? I found out pretty much to "just work" and with a really good performance too.

Re: Xrdp: An open source RDP server

#35
And then there is Teradici’s PCoIP hardware, which is shockingly good. It compresses and encapsulates video, audio, and device data. You just install a card into your machine at one end and run a thin client box at the other end - or use a software client.

The quality is amazing.

Re: Xrdp: An open source RDP server

#36
post #35

And then there is Teradici’s PCoIP hardware, which is shockingly good. It compresses and encapsulates video, audio, and device data. You just install a card into your machine at one end and run a thin client box at the other end - or use a software client. The quality is amazing.

Nvidia and Amd video cards (and probably also intel) have done the same thing for a while.

Re: Xrdp: An open source RDP server

#37
post #27

I used to maintain some linux remote desktops at my job for specific workflows of certain employees. Wow, using xrdp was a complete gong show to manage. The most common bugs were in the assignment of displays on user logon, as well as a crappy, often buggy, login screen (though GUI logins for linux are fascinatingly weird pretty much universally.) That being said, even in evaluating alternatives there wasn't anything…

> That being said, even in evaluating alternatives there wasn't anything much better. Do you remember what issues were there with NX? I found out pretty much to "just work" and with a really good performance too.

I used NX years ago. Setting it up required fiddling, and it periodically broke. TigerVNC is my current favorite for Linux servers. Cloud gaming is a different world of protocols.

Re: Xrdp: An open source RDP server

#38

I use RDP multiple times every day. I have tested Linux RDP server implementations and they are very buggy and really not production ready only NX kinda is (yet not as good as MS RDP). VNC is so bad and lacks so many features that it's not even considered a competition - it's old insecure slow protocol that should be forgotten by now.

Although VNC allows multiple users to view the same screen at the same time (and fight over the mouse if they wish).

In all seriousness though it's useful if you use VNC just to remote monitor a screen and want to leave it open indefinitely.

Also RDP uses TCP and UDP which makes it bad for SSH tunnelling, as opposed to VNC which is TCP only and easy to tunnel.

Re: Xrdp: An open source RDP server

#39

Earlier quoted context omitted.

ssh -N -L5900:127.0.0.1:5900 user@server is usually cleaner than using nc, it doesn't require running any commands on the remote system and lets you do any port changing that you need to make things work between each side.

Right, I had to use `nc` instead of forwarding the port from SSH itself because I use systemd socket activation for that ssh command, with ExecStart=ssh -T server 'nc 127.0.0.1 5900' StandardInput=socket StandardOutput=socket in the service file and ListenStream=0.0.0.0:5900 in the socket file. The socket has to be connected to stdin/stdout instead of using SSH forwarding since SSH doesn't support fd-based socket act…

Why must systemd break everything?

It is like a vandal with a baseball bat.

Re: Xrdp: An open source RDP server

#40
So a long time ago I worked volunteer IT for a fan convention. This is roughly mid to late 2000s. Among many other things, I was constantly looking for ways to speed up the registration line. And rather than have reg workers type things in, one way I hit on was to have terminals there for people to enter their own information.

Shoestring doesn't even begin to cover it. Buying computers was definitely out. So I hit on the idea of buying used Wyse Winterms. Winterms are thin clients that talk either RDP or Citrix ICA. These could be had for about $20 a pop on eBay. I would hit local pawn shops, thrift stores and recycling places to get monitors and keyboards to go with them.

But they're just dumb terminals with Windows CE on them. How to actually use them?

xrdp!

I set up a Linux system with xrdp and a bunch of X sessions for the Winterms to talk to. Took a lot of fiddling to get it right. Like I probably spent two weeks in the evenings getting everything right. But even I was surprised how well it worked. With a full-screen web browser in kiosk mode it shaved massive amounts of time off how long it took to get through the reg line.

We actually used that setup for about three years before we had enough money to invest in better hardware. Over that time I'd estimate about 8,000 people used them. But I'll always have a soft spot for those stupid Winterms and xrdp.

Post reply on HN