This really just highlights the fact that Windows ships with no tools to establish any kind of verified trust chain. No md5sum, no authenticated package management, no native ssh client. Being concerned about privacy and security and running Windows may be mutually incompatible.
Windows does come with tools to establish a verified trust chain...it's just not using ssh. I'm not sure what you mean by authenticated package management, but Windows does authenticate packages that have certificates and you can manage certificates that you trust. What else do you want to do? And I'm fairly certain that Windows comes with even more robust tools out of the box for network trust management than Linux…
Downloading PuTTY Safely Is Nearly Impossible (2014)
81–90 of 173 posts
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#82Putty is pretty awful anyway. Git for windows installs a shell that is not terrible, includes an ssh client, and is distributed over https. It is my go-to when I have to use a windows machine.
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#83Title should be "Downloading Putty Safely Is Nearly Impossible" Don't most people install stuff in Windows through Ninite when possible these days? I know it has at least one SSH client. And in my experience, the vast majority of good software is at the top of any search query.
It's the first time I've heard about Ninite. I do use chocolatey as much as possible for all windows installations.
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#84This really just highlights the fact that Windows ships with no tools to establish any kind of verified trust chain. No md5sum, no authenticated package management, no native ssh client. Being concerned about privacy and security and running Windows may be mutually incompatible.
It has HTTPS and FTPS support natively. It also supports generating hashes in SHA1, SHA256, SHA384, SHA512, MACTripleDES, MD5, and RIPEMD160 using the aptly named Get-FileHash cmdlet.
> no authenticated package management
MSI installers can (and should) be signed, and well as many other Windows installers and other binaries. Windows 10 supports "real" package management, but security is unimpacted directly.
> Being concerned about privacy and security and running Windows may be mutually incompatible.
You've given zero plausible reasons for believing so. All you've demonstrated here is that you know little about Windows and what the term "verified trust chain" means.
Just Windows supporting HTTPS alone more or less ruins your point.
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#85This really just highlights the fact that Windows ships with no tools to establish any kind of verified trust chain. No md5sum, no authenticated package management, no native ssh client. Being concerned about privacy and security and running Windows may be mutually incompatible.
Windows has an SSH-like framework for PowerShell[1]. One could argue that Linux doesn't ship with tools for connecting to non-Linux hosts, so why should Windows ship with tools for connecting to Linux hosts?
It will have package management in Windows 10 [2].
Powershell can get the hash of a file in many different algorithms.
[1] https://technet.microsoft.com/en-us/magazine/ff700227.aspx [2] https://github.com/OneGet/oneget
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#86Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#87Another reason to prefer the unix-like tools (that are included with Git for Windows ( http://git-scm.com/downloads ) but are also available separately) over PuTTY is Vagrant, it can't run "vagrant ssh" on Windows otherwise. Also, you'd always need dedicated key files because PuTTY uses PPK instead of regular OpenSSH ones.
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#88Earlier quoted context omitted.
How about the fact that it's awful? Can you seriously compare PuTTY with even the most lacklustre terminal available on OS X or Linux? It's an atrocity of UX design straight out of the Windows 95 era. Their home page is also the epitome of not caring about user experience even to the slightest degree. Nearly zero effort: http://www.chiark.greenend.org.uk/~sgtatham/putty/ I've seen people construct more impressive pag…
Wait... you think a terminal emulator, which by definition has almost no graphical UI at its heart, is crap because of its UI? Really? You think the entire program is crap because, what, you don't like how the Preferences panel is laid out?
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#89Earlier quoted context omitted.
If SSL is free and easy (especially if it's automatable) to generate through Let's Encrypt, the use case for wildcards mostly goes away.
Excuse me for being a pedant, but wouldn't Let's Encrypt end up being just another potential attack surface?
Re: Downloading PuTTY Safely Is Nearly Impossible (2014)
#90This is really just a rant about how poorly PuTTY is distributed. (and a vague implication that it is malware of some sort). I think it is a valid criticism, and I wish the person who wrote PuTTy (an SSH client for windows) would be more open/available/transparent but it is hard to force that on someone.
If there was a formal package management system in place for these OSs this would have been less of a problem from the beginning, but they're only getting around to it now as I understand it.