Hi all -
I know there is an old post regarding this, but instead of resurrecting a dead post, I felt it better to use a new one.
I've been using KiTTY instead of PuTTY with RDM 8.1+ for a while now, and it works for the most part, with one exception. KiTTY stores its session and settings in a different key than PuTTY. This means that whenever I have to create a session (pubkeys, or other session-type settings) I have to copy the keys from KiTTY into PuTTY's registry path for it to work. It would be nice to have a flag to set if using KiTTY to tell RDM to use KiTTY's registry path.
For your info, the PuTTY Reg path is:
HKCU\Software\SimonTatham\PuTTY\Sessions
And the Kitty Reg path is:
HKCU\Software\9bis.com\KiTTY\Sessions
Thanks!
edited by belthesar on 5/5/2013
edited by belthesar on 5/5/2013
I know there is an old post regarding this, but instead of resurrecting a dead post, I felt it better to use a new one.
I've been using KiTTY instead of PuTTY with RDM 8.1+ for a while now, and it works for the most part, with one exception. KiTTY stores its session and settings in a different key than PuTTY. This means that whenever I have to create a session (pubkeys, or other session-type settings) I have to copy the keys from KiTTY into PuTTY's registry path for it to work. It would be nice to have a flag to set if using KiTTY to tell RDM to use KiTTY's registry path.
For your info, the PuTTY Reg path is:
HKCU\Software\SimonTatham\PuTTY\Sessions
And the Kitty Reg path is:
HKCU\Software\9bis.com\KiTTY\Sessions
Thanks!
edited by belthesar on 5/5/2013
edited by belthesar on 5/5/2013