Serious Security Hole In PuTTY
Tim 'gk^' Nilimaa writes "A serious security hole has been found in PuTY, version 0.54 and before. Simon Tatham and his fellows released PuTTY 0.55 on 2004-08-03 which solves this bug. The bug may allow servers to use PuTTY to act as a machine that you trust, even beforce you verify the hosts key while connecting using SSH2. An attack could be a fact before you know that you have connected to the wrong machine. I (and they) say: upgrade to PuTTY 0.55 - now."
I've used Putty now and again, but I know alot of others that do use it on a daily basis...so its always assuring that the devs have a quick turn around on fixes (especially with free software), that kind of dedication is appreciated
Sehr geehrter Toilettenbenutzer!
The writeup is not clear:
The bug may allow servers to use PuTTY to act as a machine that you trust,...
Well, of course you trust your client machine.
You are being MICROattacked, from various angles, in a SOFT manner.
Open Putty, Category -> Connection -> SSH -> Tunnels.
In the port forwarding section, add new forwarded port.
Pick a source port. Any port will work, but 1080 is the standard for socks 5 proxies. Leave Destination blank, and choose Dynamic (instead of Local or Remote). Click the add button, and you should see D1080 listed in the box.
Okay, now you can save your session and start it.
In applications you can go into their connection settings section and set localhost, port 1080 as the SOCKS host. The application will then tunnel everything through your SSH connection.
I've heard lately about a lot more SSH chatter showing up than normal. There's been some speculation about an exploit turning up, soon. Perhaps this is it.
Or maybe there's Yet More To Come.
The living have better things to do than to continue hating the dead.
It appears the main PuTTY site has been Slashdotted: here's a few more links:
http://putty.obengelb.de/
http://www.puttyssh.org/
http://putty.activalink.net/
And a nice mirrors list.
Mike
Does anyone really do anything other than just blindly hit "yes" when presented with a new host identification string?
Even with strict checking on, most of us are used to blowing records out of known hosts files when they don't match, due to system upgrades causing the old records to be invalid all the time.
I've had enough abrasive sigs. Kittens are cute and fuzzy.
Why isn't this on the front page? Oh, right, let's bury news of problems with cool programs, but a minor issue (solved six months ago) in a Microsoft program gets front page mission.
Keep up the good work Rob. Hey, where are the 503's today? It hardly seems like the dot without them.
Yeah, yeah, -1, flamebait -1 troll. Who gives a crap? Not Rob or OSDTNVHPR
Jesus was all right but his disciples were thick and ordinary. -John Lennon