PuTTY 0.61 Released 184
drmacinyasha writes "Simon Tatham announced Tuesday the official release of PuTTY 0.61 after four years of development. It brings a number of bug fixes and improvements, such as GSSAPI SSH-2 authentication, significantly faster SSH key exchanges, and even support for Windows 7's jump lists. Downloads are available from the project's homepage."
Self-deprecating version numbers are the suck (Score:0, Interesting)
Ok, we get it: you're not comfortable saying it's "release quality" yet. But *%@# it's been 4 years since you bothered to release an update; that means it's pretty darn stable. Go ahead and take the plunge and call it 1.0. Qualify that as BETA or something if you have to, but please stop calling it 0.xx.
Re:PowerShell Integration? (Score:5, Interesting)
The thing about Putty is that it's a self contained executable, which means you can throw it on the flash drive that's already hanging from your key ring. No need for cygwin or whatever. Nothing to install on the host system.
Some of us have full Linux distributions there and various Windows tools for fixing busted Windows machines.
Where's yours?
--
BMO
Simon Tatham is my hero (Score:2, Interesting)
I don't always run Windows, but when I do, I prefer PuTTY
Re:Link (Score:3, Interesting)
Use Kitty instead. Having said that, clickable links don't always work correctly.
That is, unfortunately, true of pretty much everything that Kitty provides as a value-add for Putty. Everything almost, but not quite, works. I really, really wanted to like Kitty (it adds a ton of neat features to Putty), but after about two weeks of frustration I went back to Putty.
Re:Self-deprecating version numbers are the suck (Score:5, Interesting)
Hopefully the esteemed Mr Tatham won't mind if I quote him directly, but in 2007 he wrote this about why puTTY wasn't version 1 yet:
But that's not primarily what's holding back a 1.0 release. The real thing I want to do first is to sort out the data storage: there are quite a few features on the wish list which would require a revamp of that, such as
- ability to store some settings in HKEY_CURRENT_USER and others in HKEY_LOCAL_MACHINE, so that a sysadmin could set up some default saved sessions and a default host key cache which would then be the starting point for each user's personal configuration
- inheritable saved sessions (so that when I change, say, my font preference in Default Settings it automatically propagates to all my other sessions _except_ those in which I've specifically asked for a non-default font)
- storing configuration in a disk file as an alternative to the registry (so that people can carry around PuTTY plus their config file on a USB stick)
- ability to configure all PuTTY's options from the command line (rather than having to do a lot of them by the cumbersome method of creating a saved session and using -load).
Now I'm not saying I want to have _implemented_ all those features before 1.0, but I want to have made a commitment to a data storage format which is capable of supporting them. Currently PuTTY's data storage only tries to be upward- compatible, meaning that you can upgrade PuTTY and it'll still work with your old settings. Use an older PuTTY with newer settings, and you're on your own. My goal is that within the 1.0 series, the data storage should be compatible in _both_ directions. (Not because I anticipate people deliberately downgrading PuTTY, although it's been known occasionally, but because I can easily imagine people using different versions on two machines which happen to be sharing a network-stored configuration.)