Portable PuTTY patch comments

From: Charles Appel (cng_at_appelmail.com)
Date: 06/13/04

  • Next message: John Riddoch: "Using pscp from a Windows service" 
    Date: Sun, 13 Jun 2004 01:14:43 GMT

    All:

    I've created a patch to allow PuTTY (Windows) to read settings from file
    instead of the registry.

    WHY: Although the workaround suggested in the docs (4.2.1 Storing
    configuration in a file) works well, I accidentally overwrote then
    deleted a friends HKCR\Software\SimonTatham\PuTTY registry entry when
    running PuTTY from an admin CDROM I use.

    I had sent the developers a detailed proposal that I was planning to
    implment several months ago, but never heard back. So, I'm looking for
    user feedback. My objective is to modify/patch as few files as possible
    in the hope that the patch will actually get included

    Right now I have putty.exe working, using the same methods for
    reading/writing that the ux source does. Actually it's a copy of the
    code, with a few modifications. I would have liked to use the uxstore.c
    code, but that would have involved too much refactoring, which, although
    simple, might lessen the chances the patch would ever get implemented in
    the main tree.

    So, I'm looking for feedback on the following: Should the patch store
    files in the same way the unix code does (multiple files in a config
    dir), or should it be in a single file, like an INI? As I see it, pros
    and cons of both:

    INI Pros
    - One file, easy to grab and go
    INI Cons
    - Could get big, depending upon how many sessions/keys are saved
    - If it is big, and run from a floppy (who does that?) could be slow to
      read and write.
    - Can't share/distribute a single session with someone.

    UX Method Pros:
    - Much easier to implement since 99% code comes from uxstore.c
    - Can share/distribute a single session file
    UX Method Cons:
    - When taking PuTTY on the road, must copy config dir instead of one
      file

    Factors in making a decision (in order of priority)
    1) PuTTY dev team rules
    2) Lots of responses: majority rule
    3) Few responses: whatever is easiest rules
    4) No responses: my own Personal Portable Putty Patch mmm.. PortaPuTTY

    When completed, I guess I'll post the patch here since I think email to
    PuTTY dev team goes to /dev/null. Or should I post somewhere else?

    Finally, if anyone has comments on the randomseed file:
    I'm not really sure why this is stored; it gets changed everytime
    you run PuTTY anyway. I'm thinking of not storing it (since, you
    won't be able to if running from CDROM anyway). Thoughts?

    Regards,
    Charles Appel

  • Next message: John Riddoch: "Using pscp from a Windows service"

    Relevant Pages

    • PuTTY - patch to allow tiling on windows
      ... I have been using PuTTY (on windows) for a half year now, ... But I was able to patch PuTTY to fix this problem. ... It can be applied like this: patch -u window.c tilepatch ...
      (comp.terminals)
    • Re: AIX patch works for Openssh but not Putty
      ... >>I have applied a patch to openssh to get it working with AIX password ... If I ssh to the daemon using openssh ssh it works fine. ... > As far as I know PuTTY does not handle PASSWD_CHANGEREQ. ...
      (comp.security.ssh)
    • Re: The Putty Problem
      ... > PuTTY_is1 export the keys as *.reg files. ... > floppy disk with your PuTTY program. ... > the registry record it. ... Except it's easy to merge the two exported reg files (three? ...
      (alt.privacy)
    • Re: cloning PuTTy on second W2K box
      ... but am getting error accessing registry this is with regedit. ... There is info on this at the PuTTY download site. ... its settings on one floppy, you probably want to store it on the ...
      (comp.terminals)
    • Re: cloning PuTTy on second W2K box
      ... Any idea why there was no registry entry ... but am getting error accessing registry this is with regedit. ... It is also curious that after installing PuTTY 0.58 there is no registry ... its settings on one floppy, you probably want to store it on the ...
      (comp.terminals)