Royal Apps

Hi Stefan,

Thank you for your great product.

RoyalTS already has the support of custom Putty executable. That is awesome because RoyalTS users can use latest versions of Putty as soon as possible.

RoyalTS generates custom Putty session (TEMP_SESSION_*) and runs Putty with it:

putty.exe -load "TEMP_SESSION_67613" -pw "lystor"

But the problem is that the RoyalTS does not support all options of Putty. Also Putty adds new options with new releases or changes existing.

Please add to RoyalTS the possibility to input the name of existing saved Putty session in properties of "Terminal Connection". RoyalTS should set it in Putty args with ssh hostname and username.

Example:

putty.exe -load SESSION_NAME -ssh localhost -l lystor -pw lystor

https://the.earth.li/~sgtatham/putty/0.72/htmldoc/Chapter3.html#using-cmdline

This will give users RoyalTS the ability to use all the functionality of Putty and existing Putty sessions with tons of tweaks.

Thank you

Regards,
Mykola

Hi Stefan,

The issue persists in 5.1.10927 / 5.01.11001.0 / 5.01.11003.0 with both default and custom Putty executable.

%appdata%\code4ward was removed on each test.

Custom Putty profile was created with default settings.

The issue absent if type "SSH connection" is used instead of "Existing Putty Session".

STR:

1. Create new document

2. Add new terminal (putty)

- Display Name: test1

- Connection type: Existing Putty Session

- Putty Session: test1

- Computer Name: 10.10.21.21

- Credential: Specify username and password

- Username: root

- Password: root

Process:

"C:\Users\lystor\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe" -load "test1" 10.10.21.21 -l root -pw "root"

OS: Windows 10

> Can you check the PuTTY setting under Windows -> Behavior

I have the same settings as yours.

> Is it possible that your template session you are using is configured to use a custom window title? 

Nope

I have removed the branch Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\ using Registry Editor and created new session with all default settings using C:\Users\lystor\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe.

P.S. On first connect to new host (when Putty displays "Putty Security Alert" dialog with new fingerprint and user should press "Yes / No" button) RoyalTS always connects to Putty process.

On second connect to the same host (when fingerprint is already saved into Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys) the issue occurs.

Hi Stefan,

Hmm

I am not able to reproduce the bug in VM with clean Windows 10 (version 1903).

It exists on my primary PC with Windows 10 Enterprise LTSC (version 1809).

Sorry, I can't create the video on that PC but I can send you any additional required information (process list for example, etc).

Hi Stefan,

Thank you for this feature.

It is amazing!

---

But I found a small bug in 5.1.10920:

RoyalTS sets HostName + UserName + PublicKeyFile keys in Windows Registry for "SSH Connection" type but it doesn't set PublicKeyFile for "Existing Putty Session" type so private key authentication doesn't work.

---

I think RoyalTS should not change the existing Putty profile and always pass hostname + username + password + private key in Putty command line (for example once username is saved in session, Putty will never ask for it but usernames and keys may differ between hosts):

# putty.exe -load SESSION -ssh localhost -l USERNAME -pw PASSWORD
# putty.exe -load SESSION -ssh localhost -l USERNAME -i PRIVATE_KEY.ppk 

Thank you

v5.1.11003

The issue exists only in connection type "Existing Putty Session" with both versions of Putty (built-in 0.71 and external 0.72).

The session "profile1" were created with built-in Putty 0.71 and has default settings.

Connection type "SSH connection" doesn't have this bug (both versions of Putty works fine).

Command lines:    

"C:\Users\nikolay.ul\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe"

-load "profile1" 10.10.21.21 -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk" 

   vs 

"C:\Users\nikolay.ul\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe"

-load "TEMP_SESSION_45482" 10.10.21.21 -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"

---

"C:\Program Files\Putty\PUTTY.EXE" 

-load "profile1" 10.10.21.21 -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"

 vs   

"C:\Program Files\Putty\PUTTY.EXE" 

-load "TEMP_SESSION_69167" 10.10.21.21 -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"

It seems like RoyalTS uses invalid regexp to search for Putty process if "Existing Putty Session" used.

EDIT: built-in Putty version is also 0.72, not 0.71

I have attached screenshots and HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\profile1

https://i.postimg.cc/sD9kQ6Tc/s1.png
https://i.postimg.cc/Vkf3jqTc/s2.png
https://i.postimg.cc/kGPHDK8z/s3.png