Best way to do remote development?

S. Dale Morrey sdalemorrey at
Sat Jan 12 11:32:43 MST 2013

Just an FYI, I do have much more than basic sysadmin skills.
By horribly insecure I was referring to the protocol, running VNC
without tunneling via SSH is just as bad as telneting in.

When I mentioned that I don't know enough to know how to secure it, I
was just trying to say that the protocol is badly broken and I'm not
sure what alternatives there are/were.

I have been doing some research though and it turns out that terminal
services via RDP does appear to be encrypted and you can set the
encryption level in the xrdp config file.
Why the heck it defaults to low I don't know though, so maybe someone
can explain that one to me.

On Sat, Jan 12, 2013 at 10:17 AM, Michael Torrie <torriem at> wrote:
> On 01/12/2013 08:51 AM, Alan Young wrote:
>> On Sat, Jan 12, 2013 at 7:38 AM, S. Dale Morrey <sdalemorrey at> wrote:
>>> I'm an IDE addict, things like code completion and other bells and
>>> whistles are important to me.
>>> The latency introduced from an RDP connection to my already overtaxed
>>> desktop, over the anemic upload speeds of my ISP, would virtually
>>> guarantee the remainder of my hair falling out ;)
>> Vim has all of that.  I gather emacs does too.  If you're dead-set on
>> a graphical environment, setting up a vps (linode, or aws, or
>> whatever) and using vnc is a solution.  X forwarding is another
>> solution.
> You might also try using opennx client and the freenx server.  It's as
> fast as X can get over a remote link.  Or at least use freenx to speed
> up a VNC connection.  The only thing about FreeNX and a real X11 desktop
> that I don't like is that anytime you get disconnected it leaves the X11
> processes frozen, and if you're lucky you can reconnect to them and they
> will run again.  With the VNC solution (with or without FreeNX), at
> least they keep running without you.
> I agree with Alan, and other, though.  If you're going to work remotely,
> you need to ditch the IDE.  ssh, tmux, vim are going to be your fastest
> tools.  You just aren't going to enjoy running an IDE remotely.
> Also you'll probably want to use good version control tools (git), and
> then you can pull your code down locally to work on, then check it in,
> etc.  Put your clients on version control too so you can easily check
> out new code to their sites.
>> But, honestly, in any solution that has you logging in remotely
>> requires your gaining at least minimal knowledge of system
>> administration and security.
> True enough.
> /*
> PLUG:, #utah on
> Unsubscribe:
> Don't fear the penguin.
> */

More information about the PLUG mailing list