Mremoteng: Add support for KiTTY

[Miarka24]

There was some progress regarding portable mRemoteNG, I am using it on a network share and it is working fine. There is only one thing missing, and that is saving Putty sessions portable and not in the registry. That is especially true for publickey auth.
My current solution is to use Putty Filestorage from http://jakub.kotrla.net/putty .
Setting this up manually works fine, with one exception: the manually set path to Putty filestorage is not safed portable. It is probably saved in appdata.

My suggestion is to integrate filestorage in PuttyNG, at least for the portable edition, or maybe make it selectable and deliver two Putty versions, one with filestorage and one without, and let the user decide.

One question though, what is the difference between PuttyNG and normal Putty?

Best Regards
Jonas Stunkat

[mrPsycho]

+1

[vmario89]

i am looking for the KiTTY integration thing too because i have a really porn looking setup now - and i am only struggling with the "Default Session" because mRemote does not read the Kitty Sessions file based right now

[sparerd]

Moving my notes from a duplicate issue:

Dev notes:
To do this we will need to:

• [ ] Add a putty session provider to support loading kitty sessions from files
• [ ] Add stuff in the options page to allow defining the kitty path. We will need to decide whether kitty can be used side by side with putty or if it is an either-or choice.
  --- If kitty and putty can be used together, we need to add a connectioninfo property to define which ssh provider to use. (We will need this anyway if we ever get around to supporting SSH.net #181)
  -- If kitty will be used instead of putty, we need a way to detect that it is kitty so we can use the right session provider. Either determine this dynamically (give us a path, we will decide which provider to use), or explicitly (some toggle checkbox or drop down to declare which provider to use).
• [ ] Ensure that the connection tree node for putty connections displays "PuTTY Sessions" for normal putty and "KiTTY Sessions" for kitty to provide easy feedback to the user which provider is being used

[sparerd]

Merged two similar requests for allowing file-based PuTTY configuration. Since KiTTY is well-known, we will focus on integrating that.

[jslay88]

Just for those who want to be able to do this without official support, you can create a registry link from the KiTTY sessions to the PuTTY sessions.

First, check HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions to see if it exists. If so, export it to back it up, then delete it. You should be left with the HKEY_CURRENT_USER\Software\SimonTatham\PuTTY key. If you don't have this key, create the key path to it.

Using this tool here https://github.com/tenox7/regln/releases

You can use cmd (administrator privileges) to create the link as such, replacing regln with the binary you downloaded, and <your_user_sid> with the SID for your account

regln HKEY_USERS\<your_user_sid>\Software\SimonTatham\PuTTY\Sessions HKEY_USERS\<your_user_sid>\Software\9bis.com\KiTTY\Sessions

You can determine your SID with this command

WMIC useraccount get name,sid

After the link is created, you can restart mRemoteNG, and it should pull the sessions in as expected.

Not sure how this effects portable versions. I just stumbled onto this issue via the title of it.

[zerweck]

@jslay88 thank you for this tip, it worked perfectly. I am using the portable versions of both Kitty and mRemoteNG, so the Kitty configuration was not initially saved in the registry. Therefore, I ran Kitty once with the flag -convert-reg.

Since I was looking for a onetime export instead of a continuous solution, I did not use regln but exported the Kitty keys into a .reg file and edited the key paths to match the Putty Scheme. After a restart, mRemoteNG was able to recognize the keys.