In the OskiBox days I was looking at noVNC https://kanaka.github.io/noVNC/.
It only requires an HTML5 web browser to connect which means that people
wouldn't need any X11, vnc, or rdp clients. At the time it wasn't reliable,
however by knowing what commit to clone from you could get something that
would mostly just work.

Under what conditions do you anticipate needing to remote in to BCE? E.g.
AWS, bare metal, etc.

Ryan

On Tue, Jun 30, 2015 at 2:19 PM, Dav Clark notifications@github.com wrote:

This seems like an easy windows approach: http://mobaxterm.mobatek.net/

I had a list of potential options somewhere... but don't know where now :\

—
Reply to this email directly or view it on GitHub
#48.

There's also:

https://www.xpra.org/
NoMachine (nx)

This is for situations where students have trouble installing a VM, or when I may in the near future put BCE on a super-beefy server (the system I was talking about maybe running RHEL as the base - but then BCE in Docker or something).

I would also find a remote desktop connection helpful for cloud computing purposes, such as for syncing files with Dropbox. I tried to setup a VNC server and connect via an SSH tunnel but haven't gotten it to work yet.

With many of these protocols, the server listens on one port, but then connects on other ports (often determined at run-time). I don't know about VNC, but you might do better just opening a port range in the EC2 console or equivalent (assuming your remote desktop approach is as secure as SSH ;).

Xpra will apparently work over SSH, and @aculich (and others) have been using Xpra + Xephyr with Docker happily: https://github.com/rogaha/docker-desktop

Do you want to try Xpra out, @ck37?