This project has moved and is read-only. For the latest updates, please go here.



Hi guys,

I was thinking about using PuTTY inside Terminals. I think PuTTY is a more featured SSH client than current SSH implemented in Terminals.

To test:
connection is successfully opened when:
  • Ssh1 is used
  • Ssh hosts authentication is used
  • Ssh interactive authentication is used (no stored username/password or credential is used)
  • Ssh username/password authentication is used with stored credentials or stored username/password pair
  • Ssh certificate authentication is used, certificate associated with the favorite is used
  • Telnet connection is used
  • Test, that options are saved/loaded from the database
  • Provide as much as integration tests possible
  • Provide documentation, how to configure each type of connection in our wiki, when relevant and steps how to troubleshoot the connection issues
  • Document which server software and version was used for testing (multiple servers for Windows and Linux) where possible
  • Consider, upgrade of options from previous versions is possible, otherwise we will upgrade to default options
  • We need to redesign the credentials to more generic to able support other types of credentials (see other feature requests like support Windows stored credentials, keypass external tool)

file attachments


Yoltie wrote May 5, 2015 at 7:18 PM

Or at least implement X11Forwarding and the use of pageant for authenticating. These two fonctionality are truely missing.

wrote Jul 27, 2015 at 4:58 PM

wrote Aug 23, 2015 at 12:13 AM

wrote Oct 19, 2015 at 4:37 PM

wrote Oct 26, 2015 at 10:50 AM

KarlosChuar wrote Nov 17, 2015 at 7:55 PM

Please everybody to vote for this as replacement possibilities of current poor ssh (Granados) client.
Vote options:
A) Replace ssh by embeded Putty
B) Replace the Granados library by better ssh client.

wrote Dec 30, 2015 at 3:04 PM

wrote Jan 19, 2016 at 3:31 PM

bcrist wrote Jan 19, 2016 at 3:34 PM

We would love to use this client for SSH but I keep getting an error: Sorry, Terminals was unable to connect to the remote machine. Details: Object reference not set to instance of object. Putty works fine. So I think that Putty integration would be the best option. Also maybe a winscp file transfer integration may be nice too.

I vote A) replace ssh by enbeded putty

Jiml243 wrote Jan 26, 2016 at 1:56 AM

A - Putty

silentchasm wrote Jan 26, 2016 at 2:39 AM

A - Putty

KarlosChuar wrote Jan 26, 2016 at 9:11 PM

+10 votes for Putty because of closed work item 34776.

wrote Feb 2, 2016 at 10:27 AM

djoman38 wrote Feb 26, 2016 at 7:43 PM

A please

wrote Mar 3, 2016 at 11:47 AM

jeffporter wrote Mar 3, 2016 at 2:14 PM

Its been a year, any update on this idea?!?!

wrote Mar 18, 2016 at 3:28 PM

wrote Apr 12, 2016 at 2:47 PM

wrote Apr 19, 2016 at 8:16 PM

wrote Jun 3, 2016 at 5:50 PM

wrote Sep 7, 2016 at 7:32 AM

wrote Nov 9, 2016 at 9:03 PM

wrote Dec 18, 2016 at 7:44 PM

jorgerocha wrote Dec 27, 2016 at 9:09 PM

A - Putty.

What do you guys think about session configuration?

PuTTY stores all the session config at HKCU\Software\SimonTatham\PuTTY\Sessions and one of the best features of Terminals is having all configs at one place.

I thought as an alternative to backup PuTTY registry entry into Terminals configuration and restore it into registry if it isn't there.

other suggestions are welcome.

wrote Dec 28, 2016 at 8:04 PM

jorgerocha wrote Dec 28, 2016 at 8:04 PM

Hi guys,

I wrote a Terminals plugin to integrate with PuTTY. It's still pre-alpha stage but it's fully functional.

I would like to contribute with this, but I don't know how. I would appreciate if someone could give me instructions for it.

wrote Jan 6 at 8:10 PM

Associated with changeset 108690: Implemented basic structure for putty plugin

wrote Jan 6 at 8:14 PM

wrote Jan 6 at 9:29 PM

Associated with changeset 108692: Extracted Arguments builder from PuttyConnection

wrote Jan 6 at 9:36 PM

Associated with changeset 108693: Adding test skeleton for Argument builder tests.

wrote Jan 17 at 1:36 AM

Associated with changeset 108708: - Added pageant.exe and puttygen.exe
  • Added support to Telnet protocol
  • Added support to read session list from PuTTY registry hive
  • Adjusted tests to run against Putty plugin instead of Terminal plugin
  • Code cleanup

wrote Jan 17 at 3:22 PM

wrote Jan 17 at 4:07 PM

Associated with changeset 108709: - Added verbose option to SSH and Telnet
  • Merged with Main

wrote Jan 17 at 10:09 PM

Associated with changeset 108710: - Adjusted protocol names to SSH and TELNET
  • Adjusted icons for SSH and TELNET
  • Added support SSHv1, SSHv2 and Negotiate params
  • Added support to Pagent auth and Pagent forwarding
  • Ajusted session name save/load
  • Improved tests

wrote Apr 3 at 11:37 PM

Resolved with changeset 108789: Fixed MainForm after merge

KarlosChuar wrote Apr 3 at 11:54 PM

** Closed by KarlosChuar 4/3/2017 3:37 PM

wrote Apr 3 at 11:54 PM

wrote Apr 3 at 11:54 PM

wrote Apr 4 at 12:21 AM

Associated with changeset 108790: Fixed Putty plugin broken tests

wrote Apr 4 at 12:37 AM

Associated with changeset 108791: Code cleanup in putty plugin and tests.

wrote Apr 4 at 1:48 AM

Associated with changeset 108792: Removing code duplicities in Putty argument builder tests

wrote Apr 5 at 10:01 PM

Associated with changeset 108795: Merge from putty to Main

wrote Apr 5 at 11:00 PM

Associated with changeset 108796: Removed redundant code from Putty registry

wrote Apr 5 at 11:40 PM

Associated with changeset 108797: Code cleanup in putty

wrote Apr 6 at 12:09 AM

Associated with changeset 108798: Removed code duplicity from Putty option controls

wrote Apr 6 at 12:12 AM

Associated with changeset 108799: Removed putty branch

wrote Dec 8 at 3:18 PM