7 ms·
Good writeup, fairly made points. It'd be easy to laugh at OpenBSD finding SMTPD vulnerabilities even now (I did); but as TFA points out it's complicated and of
by h2odragon 7y ago
Good writeup, fairly made points. It'd be easy to laugh at OpenBSD finding SMTPD vulnerabilities even now (I did); but as TFA points out it's complicated and often hard to see these things.
And that's in OpenBSD which has had the honest effort and passion of scary geeks with no sense of proportion for how many years?
Compare that to the security posture inherent in projects that install with
sudo bash <(curl -sL someurl.wtf/thatredirectsanyway )
"Secure" computing today is just not going to happen. Not saying its a bad goal, or a waste of time; just that its a metaphysical pursuit of perfection doomed to beautiful failure.
- tinus_hn 7y agoSudo curl is terrible but is it really that much worse than downloading a dvd image and installing it? The main difference is how casually people give away the keys to the kingdom.
- jacobush 7y agoTo be fair there often is a key chain in place nowadays, for booting a PC. It's a little bit better even though I don't like how basically Microsoft controls the keys.
- Hitton 7y agoIt is worse. Notice that h2odragon didn't include "https" on purpose because of how many these install instructions do the same.
- jagged-chisel 7y agoDVDs also don’t implement https, and DVD images can download over http.
- zeveb 7y agoBut at least with a DVD you have the actual physical copy of what was installed, and you can examine it forensically after the fact, and you may even be able to use it as evidence of wrongdoing. You can't do that with some random file that you downloaded at some point in time (this, incidentally, is why in-browser crypto is hopelessly and forever broken).
- clarry 7y agoI can download DVD images over insecure transport and then check their signature. Not so if I'm piping code straight to shell from a http server.
- steerablesafe 7y agoI never saw a curl | bash install instruction without https.
- Hitton 7y agoYou are lucky. Last time I saw it here on HN less than week ago. When I called an author out about this I was called rude and ignorant and apparently doing so is "nasty" "especially since this is a well-known point of disagreement—not to mention well-trodden, therefore generic, therefore predictable, therefore tedious, and therefore mostly off-topic". The software in question was https://github.com/txthinking/nami https://github.com/txthinking/nami
- clarry 7y agoThe thread in question: https://news.ycombinator.com/item?id=22701891 https://news.ycombinator.com/item?id=22701891 Dang disappoints me again.
- irishsultan 7y agoOne issue with sudo curl is that it may end up your system in an unusuable (or unknown) state, even if the script you're fetching is not malicious, because your connection can be interrupted and bash will start executing even before the script is fully downloaded.
- vbezhenar 7y agoIt won't happen for properly written script.
- Someone 7y agoIt is a lot less likely, but it can happen when you first download and then execute a script, too. Disk read errors may prevent running the entire script or the script may run out of memory, disk space, or other resource limit such as the maximum number of open files or the maximum length of a file path.
- pjmlp 7y agoIt will happen, slowly but it will, liability law suits and media exposure just need to increase, then more companies will start paying attention to security.
- jstimpfle 7y agoI think some people just need to step up instead of only evangelizing, and actually build something that is useful and "secure" Oh wait... There are actually tons of such projects. Why did they not take off? (I'm trying hard not to sound cynical because I don't really know that there is absolutely no way that they could, but also I do feel cynical)
- wyager 7y ago> There are actually tons of such projects. Why did they not take off? Secure computing requires a relatively low time preference to be economical. Or, more precisely, marginal demand for secure computing increases with a marginal decrease in time preference. Most companies have (artificially inflated) high time preferences, so it's not economical for them to adopt what we consider secure computing. This is, I believe, to the net detriment of human society as a whole (at least, at my personal time preference). I'm not going to get too much into why time preferences are so (artificially) high on here, but I encourage people to look into it themselves. A lot of it has to do with government economic intervention, especially around monetary policy.
- marcosdumay 7y ago> A lot of it has to do with government economic intervention, especially around monetary policy. Don't single it out. Fiscal policy is as much guilty as monetary one. Even civil and criminal legislation help here.
- wbl 7y agoRates are low, which signals willingness to invest long term. Are you sure you got the monetary policy right?
- odkamkfn 7y agoOpenSMTPD has only been going for 7 years and it's gone through a bunch of changes almost every OpenBSD release.
- cat199 7y ago> laugh at OpenBSD finding SMTPD vulnerabilities even now OpenSMTPD is a relative newcomer - Sendmail: 1983 Exim: 1995 Postfix: 1998 OpenSMTPD: 2008 (2013 as active MTA in OpenBSD)
- JdeBP 7y agoThe counterpoint to that is that there is a lot of prior art, and prior mistakes to learn from, for something begun in 2008. So the assumption that it will take the same length of time, and the same learning and development process, to reach parity with other softwares has a flaw.
- nine_k 7y agoI suppose you don't do the `curl | bash` thing on your server fleet? I see how desktops (laptops) are more or less screwed because of the need to run ad-hoc things. But servers, which are much more controlled ad limited environments, could be more secure. A lot of orgs follow rather sane software security policies; if the software itself were less vulnerable, it would help. For a lot of end users that would make a significant difference, because they run most of their critical software in the browser anyway.