simont: A picture of me in 2016 (Default)
simont ([personal profile] simont) wrote2004-02-12 11:53 pm
  • Add Memory
  • Share This Entry

(no subject)

So I've been trying to get a PuTTY release out for some weeks now; and finally I found time to actually do the deed this evening. So I worked my way through my extensive and brand new checklist of How To Do A Release and, satisfied, wandered off to the pub.

Three hours later I return to find that I failed to set the correct permissions on the actual program files, and furthermore about sixty-four people have mailed me to point this out. Up until then I was feeling pretty smug. Oh well…

Flat | Top-Level Comments Only

[identity profile] angoel.livejournal.com 2004-02-13 01:38 am (UTC)(link)
It's good to have fans ;)

[identity profile] tsal.livejournal.com 2004-02-13 07:22 am (UTC)(link)
heh.. either way, good job on the new release. unfortunately, i have found your LJ, so i'll have ways to bug you other than email ;)

btw, what made you decide to make a gtk version of the clients?
simont: A picture of me in 2016 (Default)

[personal profile] simont 2004-02-13 07:35 am (UTC)(link)
I did each bit for a different reason, in fact :-)

In late 2002 I decided the PuTTY terminal emulator had reached a level of maturity where I actually preferred it to any of the xterm-like programs available, and it was a shame there wasn't an xterm-alike using my terminal code. So I sat down and wrote pterm.

Then I ported the SSH code to Unix, not because Unix needed any more SSH clients but because I wanted to run the fantastic valgrind debugging tool over it. Which I did, and it was very useful and found all sorts of things that I was then able to fix on Windows as well.

Then I did a Unix port of the configuration dialog box, largely as a proof of concept to make sure that my new portability interface for it actually could be used to write more than one different working implemntation. (The real aim of that work was to benefit the Mac port, but I could only test it under Unix myself because I don't speak Mac.)

After that, having done the terminal emulator, the SSH code and the config box, there really wasn't a lot left at all, and it was the work of only a few hours to tie them together into an actual PuTTY application, so I thought I might as well :-)

A command-line Unix PuTTYgen is something I've been meaning to write for ages because people keep wanting to do automatic conversion of Unix SSH keys to PuTTY format, so that was obviously worth doing.

I'd like to write my own Unix SSH agent, because there are features I'd like to put in it which I can't see OpenSSH's agent supporting in the near future. (Notably integration with X, so you can load your keys encrypted and have the agent prompt for your passphrase the first time you try to use them.)

Re:

[identity profile] tsal.livejournal.com 2004-02-13 07:45 am (UTC)(link)
Well, I'll definitely have to check out the unix version of the client. I'll test it out on the OS X server I have here, as it's got GTK and X installed on it.

Also, I might be able to finagle you some compile time once we get our new OS X Server up.

You also might want to check out the Apple Developer (http://developer.apple.com/) page, as they have tons of resources available for Mac OS X's API's. They also have info on the X11 port distributed with OS X Panther

Also, I went to check out the valgrind page, and there's a new link - you might want to update your bookmarks. :)

http://valgrind.kde.org/
simont: A picture of me in 2016 (Default)

[personal profile] simont 2004-02-13 07:47 am (UTC)(link)
That wasn't my bookmark - that was Google :-) I forgot to check the link worked before posting that comment...

Someone else is already working on an OS X port. If it succeeds, I might be forced to buy a Mac to play with it :-)
Flat | Top-Level Comments Only