Remote Terminal 1.4.0 now available

In this update I added two requested features, which I have combined into a single user interface:

"Copy" function and clickable URLs
You can find the new "Copy/URL Mode" button on the bottom AppBar of the terminal page, to the right of the Paste button. I have implemented it so that a smaller copy of the current terminal screen is displayed in front of the normal terminal. In this terminal screen copy the text can be selected and copied (including formatting), and URLs are clickable. I suspect that the URL parsing method is not perfect yet, please report any unexpected behaviour and I'll fix it for the next update.
Updates to the terminal that are happening while the Copy/URL Mode is active have no effect on the terminal screen copy.
The Copy/URL Mode can be closed by clicking/tapping the Copy/URL Mode button again or by clicking/tapping the dimmed area around the terminal screen copy, where the original terminal can be seen. It is also closed during screen resolution/orientation changes.

Other changes:

• Fixed the "Purchase" button that is displayed on the favorites page when the app is running in trial mode. Now it's possible to buy the app without leaving it.
• Fixed a possible crash when the terminal view of an SSH connection is resized (e.g. snapped/unsnapped) after the SSH connection has been disconnected
• Fixed connection errors when pressing any keys after the connection/private key password entry but before the connection is fully established

This update completes the most requested feature: Copy & Paste. I hope that I have implemented it in a useful way for everyone. If you are having issues with it please report them to me.
The next update will of course also be focused on user requests, which I try to prioritize reasonably.

Thanks to all of you for your continued support and for the nice store reviews! I am reading every review, so for those of you making suggestions or offering criticism, I hear you!

Remote Terminal 1.3.1 now available

In this bugfix update I corrected the following issues:

Empty channel data messages
A friendly Remote Terminal user reported a problem with his Cisco firewalls. He could connect but when he tried to enter the password for the enable command there was some strange output (repeated password prompts) and after two entered password characters the authentication immediately failed.
With his help I was able to reproduce the problem and find the issue: after each sent channel data message (which is sent when e.g. a key press is sent to the server) followed another channel data message without any content.
This was easily fixed and apart from the connections to Cisco firewalls, where it fixes a serious issue, every other connection should benefit from this too because of the reduced overhead.

Ctrl+Space
emacs should be much more useable now that Ctrl+Space correctly sends 0x00 instead of a normal Space.

Alt key combinations
Only 0-9 and a-z are working at the moment, every other Alt key combination is ignored. Because of WinRT restrictions with keyboard input I'm not sure if other Alt key combinations are possible.

Backspace and Ctrl+Backspace
Backspace now sends 0x7f (Ctrl+?) instead of 0x08 (Ctrl+H), Ctrl+Backspace now sends Ctrl+H. This is also the default setting in putty and should fix Backspace in emacs. I didn't encounter any problems with this but if anyone does please report it immediately so that I can add a connection setting for this!

Alternate screen buffer
The missing alternate screen buffer was added to the terminal emulation. This should be noticeable when quitting full-screen applications like text editors, where the screen from before starting the full-screen application will be restored.

Handling of unexpected connection terminations
I fixed a possible crash when a connection is terminated unexpectedly. This should fix stability issues with app suspending and resuming when connections are terminated while the app is suspended.

I'll try to add some useful features to the app in the next update so please bear with me if it takes longer than this one.
Thank you all for your support and for helping me find those bugs. If you find some more or if you have a feature request, you know how to reach me.

Remote Terminal 1.3.0 now available

In this update I added three requested features:

"Paste" function
You can find the Paste button on the bottom AppBar of the terminal page. I'm still trying to implement a useful "Copy" function.

Customizable base colors
The color settings can be accessed through the settings charm (default: swipe in from the right display edge or point the mouse cursor in the bottom right corner). Color settings are currently the only app settings which use the settings roaming feature of Windows Store Apps, which means they should be roamed automatically to multiple devices where you install Remote Terminal with the same Microsoft Account.

256-color support
Full support for 256 colors was added to the terminal emulation, which means you can now use your vim color schemes in Remote Terminal.

Other changes:

• Fixed rare terminal redrawing bug (e.g. with the Ctrl+K bash command and maybe some other commands which erase part of the screen)

The next update will be focused mostly on bugfixes. If you have found a bug you want to have fixed please write a blog comment or an e-mail if you haven't already. If you mention bugs in Windows Store reviews it would be very nice if you could take the time to drop me a line or two via e-mail because then I am able to direct further questions to you which could help me in fixing the bug.

Thanks to all of you for your continued support and for the nice store reviews!

Remote Terminal 1.2.0 now available

In this update I added two often requested features:

Full-screen terminal view
This was, understandably so, by far the most requested feature. First I tried to add the option to switch between the old "windowed" view and the new full-screen view but while I was doing that I decided that the full-screen mode is the only one that makes sense anyway, so I just dropped the old view completely. I suppose nobody is going to miss it. This feature also fixes the problem that a few lines at the bottom of the terminal are covered by the on-screen keyboard in some configurations.

SSH Private Key Agent functionality including Agent Forwarding
This was an interesting feature to add because there was no previous support for it in SSH.NET, of which I am using a modified version in Remote Terminal. The Private Key Agent can be accessed from the bottom AppBar on the favorites page where private keys can be loaded/unloaded. To be used it must be selected as the authentication method of a connection. Agent Forwarding (OpenSSH-style, which is the only one used, to my knowledge) can also be activated for each connection separately. Please do not expect SSH-1 keys to work. Although they can be added and deleted through the Agent Forwarding feature, they are neither displayed inside Remote Terminal, nor is the actual authentication working when forwarding the agent to an SSH-1 server.

Other changes:

• When the App is running in trial mode the remaining days are displayed on the favorites page
• Added missing implementation for ANSI terminal escape sequence CSI@
• Fixed crash when switching to a disconnected terminal
• Fixed crash related to ANSI terminal scroll regions
• Fixed unexpected disappearance of terminal lines after screen size/orientation changes

 As always, thank you for your feedback, which is mostly very positive! I am happy about every comment, e-mail or App review.

PS: To whoever is responsible for certifying this update at Microsoft: Thank You! It took a mere four hours from submission to publication in the store!

Remote Terminal 1.2.0 preview

First things first, here are the changes for the next version of Remote Terminal which will hit the store a few days from now:

New Features:

• Full-Screen mode (playing well with the on-screen keyboard)
• Private Key Authentication Agent functionality including Agent Forwarding (OpenSSH-style)

Other changes:

• When the App is running in trial mode the remaining days are displayed on the favorites page
• Fixed crash when switching to a disconnected terminal
• Added missing implementation for ANSI terminal escape sequence CSI@

The development of this update was a bit delayed due to the complexity of the Agent Forwarding feature...but it is almost done now and you can expect a release sometime this week (instead of last week, which I had originally planned).

As always, thank you for your feedback, which is mostly very positive! I also understand the reasons for negative feedback since some features are still missing which a few people absolutely need to get their work done. Please rest assured that I am taking these issues seriously, all the features requested so far will be implemented sooner or later. It just takes some time since I am developing Remote Terminal exclusively in my spare time.
Nevertheless, thank you for your support and keep the feedback coming!

Remote Terminal 1.1.1 now available

This version fixes a critical bug in Remote Terminal 1.1.0 which made every attempt to use SSH PrivateKey authentication impossible.

The SSH PrivateKey authentication was broken as a result of the complete refactoring of the internal Connection/Terminal/Screen infrastructure, which was necessary for the multiple simultaneous connections feature. Furthermore, I did not test this particular authentication method before releasing the update.
I just hope that there aren't many who have already installed the last update and for those who did, please accept my apology. Hopefully, the release of a bugfix less than 24 hours after the first user reported the problem to me counts for something.

Remote Terminal development is now back on track and I'm planning to release the next update some time next week.

Remote Terminal 1.1.0 Error with PrivateKey authentication

I'm really sorry to inform you that a serious bug has found its way into Version 1.1.0 of Remote Terminal, which was released a few hours ago. The error makes connecting to SSH servers using PrivateKey authentication impossible.

I will submit a fix for this problem to Microsoft for certification in a few minutes. If you have not yet downloaded the update I ask you to wait until the next update is released.
For those of you that have already updated: sorry, please be patient until the next update is released, which will hopefully be in less than 24 hours (the certification process of this update only took a few hours, although Microsoft claims it usually takes 7 days...).

I will make sure to test this important functionality from now on every time before releasing an update so that it won't happen again!