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

NoRemoteWinTitle: 0 (default) -> 1 fixes the issue with "Existing Putty Session" connection type.

It is set to 1 in "SSH connection" type.

May be it is better to validate the value of NoRemoteWinTitle and display a warning to user before connection?

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

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

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

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.

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).

> 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.