Thursday, December 31, 2015

Remote Terminal moved from to GitHub

Well, the title says it all. I have moved the Remote Terminal project hosting to GitHub.
The new URL is:

Although I like GitLab a lot, and also (have to) use it at work, the GitHub UI just seems so much more familiar.

The good thing about is that it provides private repositories for free, so if you need something like that, go check it out.


  1. Hi,

    Do you plan to upgrade the app as universal? Meaning it would be available on Win 10, Win 10 Mobile and Continuum?

  2. Hi, like the app but it seems to be unable to use "@" character. I use it on Win10 with Danish keyboard layout.
    I've tried copy / paste the character as well as using on screen keyboard but issue remain.

  3. Great app. I use it to connect to a couple of Linux boxes here, and a Linux server hosted remotely (all via SSH2). The only problem I have with it is that it often seems to simply disconnect (probably crashed) if I leave it running a long compile on a remote host. (Most recently I came back to find the app had closed and my GCC compile (which takes a while) that I left running on a remote machine had aborted when its terminal closed. Unfortunately I have no choice but to fall back to another ssh client, but I still use RT for interactive stuff. It'd be great if it were a little more stable. I have no idea what causes it to crash but Im guessing its a network error with all the incoming output from the host. (compile messages). I'm still looking for a decent win10 GUI SSH client that can handle multiple sessions. I like RT, but this makes it hard to use in an environment where connections are expected to stay connected for long periods.

  4. Great app, thank you! However, I am running into a problem with login via keys, resulting in the following error on my server: "sshd[15368]: fatal: mm_answer_moduli: bad parameters: 2048 2048 1024". After some digging, I found that this has something to do with SSH.NET and new stricter defaults on the server side (in my case, Ubuntu 16.04 LTS). See I confirmed that this is the issue by testing basic6's suggestion to limit the kex algorithm to diffie-hellman-group1-sha1 on the server. Under that limitation, Remote Terminal connects fine. However, as also stated in the post, this breaks regular connections and is unsafe. Would this be something that you could address by rebuilding Remote Terminal with the latest ssh libraries? Thanks again for a terrific app!