News for hackers. Stuff that matters.
Re:How to implement HTTPS in an insufficient manner by dragcdxfbv on Thursday April 04, 2013 @06:52AM (#5491901)
Do i have to pay or create accounts on third party services to use HTTPS (in nginx)?

I never used https on my sites because there are some giant warnings ("dangerous") in browser when you go to a website that is self-signed. No warnings on plain http.

Re:How to implement HTTPS in an insufficient manner by JennyZ on Thursday April 04, 2013 @06:55AM (#5491910)
You can get a free SSL certificate at https://www.startssl.com/ , so that should not be a reason to keep you from using it.

I do agree that the extreme mistrust of browsers towards self-signed certificates is an odd thing.

Re:How to implement HTTPS in an insufficient manner by derefr on Thursday April 04, 2013 @07:23AM (#5492001)
> I do agree that the extreme mistrust of browsers towards self-signed certificates is an odd thing.

No, not at all; it's the whole point of SSL. The guy MITMing an SSLed website can create a cert for that site himself, but he can't get it signed by a CA. So he has to sign it himself. Thus, from the browser's perspective, all self-signed certs are possible instances of "there used to be a CA-signed cert here, but now you're being MITMed."

Now, that's not to say something like self-signed certs wouldn't be nice--given some sort of distributed pin cache, we could have something closer to an SSH/PGP model where everyone's current self-signed cert "fingerprint" is on file, and alarm bells go off if you see a cert different from the one you're supposed to see. But without that, self-signing is literally no more secure than no SSL at all: anyone else can also self-sign to MITM you.

Re:How to implement HTTPS in an insufficient manner by claudius on Thursday April 04, 2013 @07:30AM (#5492021)
> but he can't get it signed by a CA.

I strongly doubt that.

Re:How to implement HTTPS in an insufficient manner by derefr on Thursday April 04, 2013 @07:33AM (#5492033)
Well, like I said--it's the whole point of SSL. If he can (and the CA responsible isn't immediately shut down), it means SSL is fundamentally broken.
Re:How to implement HTTPS in an insufficient manner by lmm on Thursday April 04, 2013 @09:00AM (#5492311)
It's free but they charge you to revoke a certificate, which is quite unfortunate as it discourages people from revoking if they e.g. leak their private key.
Re:How to implement HTTPS in an insufficient manner by dmm on Thursday April 04, 2013 @10:25AM (#5492826)
Browsers mistrust self-signed certificates because that's what a MITM attack would look like.
Re:How to implement HTTPS in an insufficient manner by claudius on Thursday April 04, 2013 @07:18AM (#5491975)
You could also think about getting CAcert(ified?) and promote the CAcert root certificates getting included in more browsers. This is not measurably more insecure since SSL is mostly snakeoil anyways as long as you rely on external entities[0] to verify the identity of websites.

Ideally, browsers would store the certificate presented on the first visit to a website and compare the certificate presented on following visits to that stored certificate to warn the user on mismatches – so far, I have not yet found a usable implementation thereof, and especially not one more widespread than CAcert.

[0] Among them such trustworthy companies as DigiTrust, TÜRKTRUST or CNNIC.

Re:How to implement HTTPS in an insufficient manner by tacticus on Thursday April 04, 2013 @06:55AM (#5491912)
http://www.startcom.org/ has free certs for non businesses. or it's about 10$ a year for a paid one