3 ms·
Troy is not suggesting people implement HTTPS. He's suggesting they use pre-rolled services made by companies which just happens to deliver HTTPS. Using a produ
by 0xbadcafebee 8y ago
Troy is not suggesting people implement HTTPS. He's suggesting they use pre-rolled services made by companies which just happens to deliver HTTPS. Using a product may be easy, but implementing HTTPS is not.
I mean, come on. Who honestly thinks "openssl pkcs12 -export -inkey httpsiseasy.key -in httpsiseasy.pem -name httpsiseasy -out httpsiseasy.pfx" looks easy? What the hell is pkcs12? What does export mean? what's a key, pem, and pfx? What the hell is going on here? Anyone can copy and paste random commands on a command-line, but that doesn't mean you have any idea what's going on, and when you have problems, you're totally lost.
I could tell people "programming is easy!", but it would be a misleading, stupid thing to say. Writing code may be easy, but actually making a well-written, well-supported, bug-free program that works reliably outside my own computer is damn hard.
If I want more people to feel comfortable programming, I'm not going to lie to them and tell them it's easy. I'm going to tell them the truth: that it's difficult, but that there are ways to ease into it and become more comfortable with it over time, and here are the ways to do that.
Please don't lie to people to push your agenda. It sucks for the people who then assume you're telling the truth, and try to do X, and then run into problems, and curse the people who misled them. I have been in this situation many times and it always sucks. If something is hard, just say so.
- tialaramex 8y agoThis command line turns the two files everybody on the rest of the Internet cares about into the single file that Microsoft, in its unvarying quest to be different for no reason, has decided is the right choice for their software. Specifically you've got a Private Key (which your servers need, but you mustn't show to anybody and so must be very careful to protect) and a Certificate (which is a public signed document and it's fine to show it to anybody, if you lose it you can just get another copy). Completely different security profiles so it makes sense to keep them separate even though you need both... And then Microsoft says OK, let's use RSA's (the company not the algorithm) PKCS #12 to bundle these two items together into a PFX file. Now we've got a file that we'll call a "certificate" but in fact must be kept private at all times and not shown to anybody. The worst thing about PFX / PKCS #12 is that as here you're usually going to see it because somebody skipped the vital step that actually makes any of Public Key security worth having. The Subject / Applicant should always generate their own keys. If you let the Certificate Issuer make the keys, the whole enterprise is basically a charade because instead of just acting as an Authority, now they're proxying for you entirely, if they want to impersonate you they can trivially do so at any time. Security goes out the window. One of the great things about Let's Encrypt is that they illustrated that you can do this right (Let's Encrypt never sees your private keys, indeed if you mistakenly present them they'll revoke your certificate on the rationale that now the keys are revealed and the cert is worthless) without making the end user jump through technical hoops like typing in OpenSSL commands they don't understand. Your keys are made on your machine, but unless you care you don't need to know about it.
- orev 8y agoIt was a rhetorical question. The fact that you needed 5 paragraphs to explain what is going on only proves the point being made — that it is not easy for anyone who doesn’t already have an intimate knowledge of PKI.
- tialaramex 8y agoSure, but this file and the command to produce it aren't anything to do with HTTPS really, they're artefacts of the Microsoft corporation's long-standing belief that refusing to interoperate helps you lock people into your ecosystem. Troy wouldn't need this file, and thus this command, except that (as HN readers sometimes forget) he's a Microsoft MVP and so even when it's clearly the wrong choice he has to pimp the Microsoft approach if possible. A better use of Troy's time as an MVP in _my_ opinion would have been to lobby Microsoft's IIS team to get ACME integration patched into recent releases ASAP‡. If this news item was "Troy's new video demos previously unannounced ACME integration for IIS 10" then it'd actually make an impact which this (unpaid) advertisement for Cloudflare does not. ‡ Bonus points since IIS is a commercial product, cut a deal to get your paying customers one free cert from a commercial CA using the new integration.
- gnode 8y agoTo use an analogy, this is like saying your two choices are: scrub and force your clothes through a mangle at home, or take them to the laundromat to use a machine. I don't see why HTTPS can't be both simple and in-house, examples like Caddy come to mind (not that I've used or am promoting that specific program).
- peterwwillis 8y agoIf I say "cleaning your clothes is easy", that's half true. Some clothes are easy to clean. Some require permanent-press slow-cycle cleaning and a low-heat gentle dryer cycle. Some require starching and ironing on various settings. Some require you to pay a service to do it for you (dry cleaning and steam pressing). As a young adult who had to learn by trial and error how to clean their clothes properly, I can tell you it ain't always easy. If I say "HTTPS is easy", that's just false. There's no way for an average person to just figure out how to implement HTTPS by themselves. You need a special set of tools to be used in a certain way and you need to follow a guide with several steps, based on your unique use case. Or you can pay for a service to do it for you. Caddy may make things easy for some people, but some people won't be able to use it, and then HTTPS is hard again. Can you learn how to do HTTPS, so that once you've done it a few times, it's easy for you? Sure! But the same goes for cleaning your clothes, writing a program, or even playing a piano. Do it enough times and it'll feel easy. That doesn't mean anyone can do it.
- gnode 8y agoIn this case, we're talking about having an automated service (Cloudflare) manage your HTTPS, not paying a human to carry out a manual HTTPS set-up. We're talking about a self-service laundromat, not a specialist dry-cleaning service. Just like I'm able to have an automatic washing machine in my home, I see no good reason why that automated HTTPS service can't be self-hosted, with no loss of ergonomics.