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,

Putty process is forked with valid args in both username + password and username + private key combinations.

But now RoyalTS is not able to connect to Putty automatically.

It always displays "External application window not found" window.

If user selects valid Putty process RoyalTS attaches to it successfully.

Hi Stefan,

I tested 5.01.11001.0

RoyalTS now adds "-l USERNAME -pw PASSWORD" to Putty command line even if private key specified.

"-i PRIVATE_KEY.ppk" is still missing in args.

Hi Stefan,

Private key authentication still doesn't work in 5.1.10927 :(

Cause: RoyalTS doesn't pass username and private key in Putty command line (-l USERNAME -i PRIVATE_KEY.ppk)  if "Terminal > Credentials > Private Key File" set or existing credential with private key selected. Only session and hostname exist.

Without private key specified RoyalTS sets session + hostname + username + password in command line as expected.

Please fix this small bug.

Thank you

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