Slashdot Mirror
PuTTY 0.61 Released
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."
Shouldn't that make it PuTTY 12.9.9 at least?
Use Kitty instead. Having said that, clickable links don't always work correctly.
The authors would be millionaires if they charged for this. I see this software used many many places, so thanks.
Why not just install OpenSSH? Then you can run the ssh and scp command-line tools as normal. If you install Cygwin, they're probably there already. The advantage of PuTTY is that it includes its own terminal emulator, which is important because the Windows one sucks (or, did when I last used Windows - Win2K - it may be better now).
I am TheRaven on Soylent News
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
All cows eat grass!
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
Some of us have full Linux distributions there and various Windows tools for fixing busted Windows machines. Where's yours?
I haven't used Windows since 2003, so I have no more need for a flash drive for fixing them than I have a need for a smithy to make replacement horse shoes.
I am TheRaven on Soylent News
putty makes the world work. I spend 90% of my day in putty... ssh-ed from a Windows box to various Linux boxes. It has never crashed. .exe by http or ftp. If only everything else could be so perfect and simple.
I also love the download page where you can grab just the
That is how I do still use PuTTY from time to time. When it's not your machine, it's polite to only use PuTTY rather than install anything, and if you don't have admin, it's the only option. But I don't often do this, I use cygwin+mintty as preference, like on my work machine.
That's why...
I was promised a flying car. Where is my flying car?
I don't always run Windows, but when I do, I prefer PuTTY
Please note: I have decided to stop development of the PuTTY Tray patch, and I have no plans to resume it at any point in the future.
And for those people who don't have the intellectual desire to tinker away at a shell, Simon Tatham has a few puzzles for you:
http://www.chiark.greenend.org.uk/~sgtatham/puzzles/
I accept no responsibility for loss of work months due to the use of these puzzles.
Ask me about repetitive DNA
http://i1-win.softpedia-static.com/screenshots/PuTTY-Portable_23.png
Note the "Dynamic" option...
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.
Cygwin is an horrendous suite to work with. Really. Just go look at how you're supposed to guarantee what version of the Cygwin DLL your applications end up using (Hint: Delete any cygwin1.dll that's not in the System directory and hope-to-god that's the most up-to-date). It can't even co-reside with itself so the second you load up a Cygwin app it's a gamble as to what version of the DLL it will find / use and whether it's even compatible any more, and what it'll do to applications you run later on. I take it that you don't do a lot of development with Cygwin compilers because it's a minefield, and after a while, you give anything to remove that Cygwin dependency (which is basically why MinGW exists, for instance).
Also, the tools are horrendously slow. I have a Cygwin development environment that I've carried for a long while and it's stupidly slow when it comes to anything half-decent, anything that forks, etc. not to mention compatibility issues every time you have to move to a new Windows version, etc.
PuTTY, in comparison, is a single file, no dependencies, works fine and everywhere and does 99% of what you want (the example you show is the most esoteric and pointless thing I could think of to show off a console, and relies mainly on the fact that you have an ffplay that can read from pipes on Windows - nothing to do with the console, as such).
A console is a shell client. That's it. It doesn't need to integrate with my current OS / desktop, or form perfect pipes, or do anything more than necessary - it just needs to show me a remote shell on another computer so I can issue commands and see responses. PuTTY does that and does it brilliantly - so much so that I've ditched lots of serial-port comms utilities in favour of PuTTY instead because it also support just raw comms. It's also so incredibly tiny and portable (unlike your Cygwin installation) that I can literally carry it everywhere.
The only thing I *hate* about PuTTY is that all the messing about with keys should really be simplified a lot without having to resort to extra utilities and third-party addons.
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.)
-Never argue with an idiot. They drag you down to their level, then beat you with experience-
I don't find that. To be fair, he didn't start it, he was asked a sort of obnoxious question and responded reasonably.
Space game using normal deck of cards: http://BattleCards.org
And, if they do, then I'd expect them to have one - or, at least, the use of one. I wouldn't expect them to go around expecting everyone else to have one too.
I am TheRaven on Soylent News
Here here!
I didn't know Powershell still uses the crap default terminal!
PowerShell is a "hostable" shell, meaning that it can be integrated into a host (.NET) application and directly share in-memory objects and hook into the host user interface. PowerShell comes with two apps for hosting it: The PowerShell console and the ISE (Integrated scripting environment). What you are referring to as the "crap default terminal" is probably the PowerShell console. I don't know why it is crap, though. If you are thinking lack of SSH, PowerShell has a much more elegant and hassle-free way to remotely execute scripts, commands, functions and even remote jobs and events.
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
You can also throw Cygwin on a thumb drive. With Cygwin you get not only ssh but ftp, bash, perl, X, etc. and all of them are designed to work together just like Linux.
I love opening a web page that is just a black serif-font text on a white background and a few blue hyperlinks.
Seriously. It is so much easier on the eye than Web 2.0 pastel grey on slightly dark grey with blue-grey borders and green-grey highlighting of links (or whatever slashdot is using today)
To have a right to do a thing is not at all the same as to be right in doing it