Thursday, May 24, 2018

new version 2.2.6 released

Changelog
  • Bug fix: Removed ssh command line parameters when using a custom session
  • Protocol "sftp" now supported for Copy Files
  • New option to hide cluster mode window after opening connections
  • Replaced a cryptographic service provider with a FIPS compliant algorithm

Portable Edition: WinSSHTerm-2.2.6.zip

Mirror: Google Drive

SHA256 (.ZIP): 4933647F1A7ABE2486FC8E9C073FB10EC2345ACFC5E747A5348E7D0AD761C1CD

Installer Edition: WinSSHTerm-2.2.6.msi

Mirror: Google Drive

SHA256 (.MSI): 20236E5A3A6ABBEAC93BB700588037DBECA4A9F5EE37BF342549446207B281F0

4 comments:

  1. I still can't find a place to change the default terminal character encoding, something like 'Window--Translation' in putty, as servers are not all working under UTF-8

    ReplyDelete
    Replies
    1. Hi, I've updated point 4 in the FAQ section. It should be possible for you to change the charcter encoding or any other PuTTY setting by using a custom PuTTY session.

      Delete
  2. Works great!
    I have one request (and I hope it don't end up in Premium Features) - a way to save/restore/propagate settings and keys from one client install to another. Maybe using an encrypted archive hosted on google drive, dropbox, or even on an ftp/sftp/scp server, but which uses a password instead of key file so it can be retrieved in new installations.

    Yes, I see the security issues with this, however, I also know that though this wouldn't work for a Doctor's office, it would be fine for others who know and have that level of acceptable risk. Maybe add a blurb/agreement before enabling.

    ReplyDelete
    Replies
    1. Hi, we'll see if more people are requesting this.

      Delete