Linked by Thom Holwerda on Mon 15th Oct 2007 21:06 UTC, submitted by Valour
Thread beginning with comment 278474
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Oddly enough, one of the big reasons why I use Windows is PuTTY. Even when I do use OpenSSH, I learned how to use most of the features on PuTTY. PuTTY has better documentation, a simpler interface (i.e. no need to pull out vi to edit config files or deal with long command line parameters), and seems to behave with non OpenSSH servers better.
PuTTY is available for Linux, *BSD, Windows, and more. Why would you use Windows just for a terminal app when that same app runs on more than just Windows?
Problem with PuTTY is that it uses the Windows registry to store just about everything. Makes it very inconvenient to use on a USB stick. Newer versions tend to use the registry less, but you still leave tracks on every computer you connect from. Not exactly a security conscious development method.
Problem with PuTTY is that it uses the Windows registry to store just about everything.
While it still won't save config to a flat file, which seems like it would be really easy with an abstracted interface to its config routines, its docs do have some workarounds, of sorts.
Oh, and there's this, which is even up to date: http://portableapps.com/apps/internet/putty_portable
RE[5]: ... - PuTTY on USB works great
by jabbotts on Tue 16th Oct 2007 19:26
in reply to "RE[4]: ..."
http://portableapps.com/apps/internet/putty_portable
It's been a staple on my win32 USB drive toolkit for years now. No local registry changes and it works great when I don't have a true bash/ssh handy.





Member since:
2006-09-21
Well, people tend to use GCC because the competition (in the open source world) is inferior. By GCC being superior, I mean in a Microsoft sort of way: all of the extensions to the languages and dependence upon the GNU tool chain to build software tends to make it difficult to drop in a third party product.
Oddly enough, one of the big reasons why I use Windows is PuTTY. Even when I do use OpenSSH, I learned how to use most of the features on PuTTY. PuTTY has better documentation, a simpler interface (i.e. no need to pull out vi to edit config files or deal with long command line parameters), and seems to behave with non OpenSSH servers better.