Remote Terminal 1.9.2 now available

Added support for more secure HMAC algorithms
Until now only hmac-md5 and hmac-sha1 were supported.
This update adds support for hmac-sha2-256 and hmac-sha2-512 to support connections to servers that only accept SHA2 HMAC algorithms.
Additionally this may also increase security even when connecting to servers that still accept the less secure HMAC algorithms (if they also support and prefer the SHA2 HMAC algorithms).

This information is also on GitHub.

Remote Terminal 1.9.1 now available

Fixed a regression with private key authentication
Since 1.9.0 private key authentication did not work because of a threading issue.
The terminal just got stuck at a blank screen with a red border.
Password and Private Key Agent authentication was not affected by this bug.

This information is also on GitHub.

Remote Terminal 1.9.0 now available

Added the ability to reconnect a terminal using Ctrl+R after a connection terminates or breaks
The fact that connections can now be re-connected has also motivated me to change the behavior when navigating away from disconnected connections (using the top app bar).
Until now such connections were deemed not useful anymore and were automatically removed from the connection manager. Thus they didn't appear in the top app bar on the favorites page and the connection page anymore.
This was changed so that these connections are not automatically removed anymore, they are marked with a red border and have to be closed with the ✖ button in the top app bar.

This information is also on GitHub.

Remote Terminal 1.8.2 now available

This update contains an important bugfix that has prevented many users from working with Remote Terminal for some time now.

Fixed incompatibility with OpenSSH servers version 7.2 or later
Connections with OpenSSH servers 7.2 or 7.3 were just not possible because a "data outside the valid range" error message just kept popping up.
This was fixed by updating the supported Diffie–Hellman group key exchange group sizes for the SSH.NET implementation used in Remote Terminal.

This information is also on GitHub.

The history and future of Remote Terminal development

Remote Terminal is an SSH-2 and Telnet Terminal Emulator which lets you
connect to your UNIX and Linux servers, NAS, VM hosts, virtual
appliances, routers and every other system supporting SSH-2 or Telnet
connections.

This is both the story of its development and also a short preview of what I am planning and how you can help.

Remote Terminal moved from GitLab.com to GitHub

Well, the title says it all. I have moved the Remote Terminal project hosting to GitHub.
The new URL is: https://github.com/spodskubka/RemoteTerminal

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 GitLab.com is that it provides private repositories for free, so if you need something like that, go check it out.

Remote Terminal now Open-Source

Today is an interesting day for me because I am finally releasing the source code of Remote Terminal to the public.

To be honest, I am a bit anxious about this step because I have never released anything of this magnitude as open-source before.
I have tried dipping my toes into the open-source pond almost a decade ago (see .NET StreamLib on SourceForge) but that was a really small side project which didn't spark any public response whatsoever. I guess it was never intended to do so, otherwise I would have put more effort into it.
But this time I am serious. I want it to be different with Remote Terminal.

Hosting

I have chosen gitlab.com for hosting the Remote Terminal project.
For now, there's just the source code and a simple README. However, in the next days I will fill the issue tracker with some open issues that were reported to me by users of the app and maybe add some kind of instruction on how to build the project from scratch (which should be pretty straightforward).

Licensing

Remote Terminal is licensed under the GPLv3 license.

Contributing

Any contributions are welcome. Really, anything that improves the functionality, versatility or documentation of Remote Terminal is welcome. I should warn you though, I am neither an experienced project manager, nor really familiar with pull/merge requests or open-source collaboration (yet). So please bear with me if I don't get everything right in the beginning.

Also, I hope that I have made a decent enough (manual...) migration of the TFS repository I have used for development until the latest release. I didn't really get the branching model back then and made strange merges of single commits that I have translated into cherry picks during the migration. I guess it doesn't really matter anymore since the Windows8.0 branch is really a throw-away branch now.

At my workplace we started a transition from Subversion to Git a few months ago and while evaluating our development model and best practices we came across the following two blog posts which we found very useful. I have decided to follow these guides in my private projects too so they shall be the base for further development on Remote Terminal.

• How to Write a Git Commit Message by Chris Beams
• A successful Git branching model by Vincent Driessen

If you want to contribute and have any questions regarding the source code, for example how different components/classes are working together, please don't hesitate to contact me. I'll be more than glad to answer your questions.