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?
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
It seems that the connection specific key file settings are not honored anymore. Thanks for bringing this to my attention. I will fix this for the next release.
Regards,
Stefan
Hi again! I've just uploaded a new build which should resolve this issue:
https://download.royalapplications.com/RoyalTS/RoyalTSInstaller_5.01.11001.0.msi
Can you download and test all the scenarios?
Thank you!
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.
I've created another build which should resolve the issue:
https://download.royalapplications.com/RoyalTS/RoyalTSInstaller_5.01.11003.0.msi
Let me know if this one works as expected.
Regards,
Stefan
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.
I'm not seeing this issue. Are you using a custom PuTTY executable?
Mykola Ulianytskyi
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