Live data from Hacker News

Our First Certificate Is Now Live

letsencrypt.org

121–130 of 263 posts

Re: Our First Certificate Is Now Live

#121
post #97
post #35

It's amazing that it takes a free provider to make things simple: https://letsencrypt.org/howitworks/ I'd actually pay more than I do now for SSL certs to get that kind of simplicity.

Looks awesome! Does anyone know if there's an undo command for `$ letsencrypt run`? I would love to try this, but too scared to do it and mess up with my nginx configs.

Perhaps $ git init your nginx configs?

Re: Our First Certificate Is Now Live

#122

This is a tiny bit odd. So they have issued their first certificate, but they don't have cross-signing in place yet? So between now and november 16th they'll be issuing a whole bunch of effectively broken certificates unless people manually install their root CA? Why even push this today if you don't have cross-signing available? Without that Let's Encrypt is effectively broken out of the box. PS - I actually like Le…

They aren't making it generally available to the public yet, only to certain beta folks who know what they are getting. It isn't broken out of the box since it isn't 'out of the box' yet.

Re: Our First Certificate Is Now Live

#123
post #82
post #63

Earlier quoted context omitted.

I run https://certsimple.com : we only do EV certificates, we're the fastest place to get an EV cert, we check as much as we can before you pay us a cent, and our application process is 80 seconds.

You might want to fix your webdesign: http://i.imgur.com/zQbWnUI.png And this is in Firefox, which renders fonts more bold than other browsers.

Just removing the font-weight: 300 helps tremendously. Personally, I'm becoming less of a fan of external fonts. I've noticed lately that they're often the slowest thing to load on sites that use them (especially Google fonts).

Re: Our First Certificate Is Now Live

#124
post #97
post #35

It's amazing that it takes a free provider to make things simple: https://letsencrypt.org/howitworks/ I'd actually pay more than I do now for SSL certs to get that kind of simplicity.

Looks awesome! Does anyone know if there's an undo command for `$ letsencrypt run`? I would love to try this, but too scared to do it and mess up with my nginx configs.

I mean... back them up? :D

Re: Our First Certificate Is Now Live

#125
post #63
post #35

It's amazing that it takes a free provider to make things simple: https://letsencrypt.org/howitworks/ I'd actually pay more than I do now for SSL certs to get that kind of simplicity.

I run https://certsimple.com : we only do EV certificates, we're the fastest place to get an EV cert, we check as much as we can before you pay us a cent, and our application process is 80 seconds.

Like the other comment says, the font is way too thin on your site and actually hurts to read on my monitor. Any interest I had in this service is effectively gone now.

Text needs to be legible, please try and stick to normal and bold weights.

Re: Our First Certificate Is Now Live

#126
post #64

Earlier quoted context omitted.

No problem :-) I actually noticed the link was HTTPS (presumably after you changed it) and thought I was taking crazy pills.

HTTP version really should redir to HTTPS.

That won't really fix anything, anyone who wants to MITM the HTTP can just kill the redirect.

Re: Our First Certificate Is Now Live

#127
post #39

Earlier quoted context omitted.

Doesn't ownership of domain.tld also imply ownership of *.domain.tld?

I don't think the owner of "co.uk" should have the power to issue certificates for everything below it.

To make the original comment more precise, should not proving ownership of:

   
be enough to imply ownership of anything under that? i.e., DNS is a hierarchy — right? At the top level (a bit closer to how the original comment phrased it, I'd say that proving ownership of,

    .
should prove ownership of all domains under that. To address the specific case of "co.uk", anyone in control of a public suffix[1] should just fail the check (i.e., owning a public suffix does not imply ownership of all subdomains, which I think is correct). Someone with better knowledge of the innards of DNS would have to speak to if the Public Suffix List is good enough here.

Really, why can't I be a mini-CA for my own domain, with only the power to issue certs for the set of domains I actually have control over? (essentially, why can't I get a nameConstraint CA cert?)

[1]: The Public Suffix list is a list of what a human might call a "tld, essentially"; "com" is a public suffix, but so is "co.uk": https://publicsuffix.org

Re: Our First Certificate Is Now Live

#128
post #63

Earlier quoted context omitted.

I run https://certsimple.com : we only do EV certificates, we're the fastest place to get an EV cert, we check as much as we can before you pay us a cent, and our application process is 80 seconds.

Like the other comment says, the font is way too thin on your site and actually hurts to read on my monitor. Any interest I had in this service is effectively gone now. Text needs to be legible, please try and stick to normal and bold weights.

I didn't know the site is unreadable until uMatrix was disabled.

Re: Our First Certificate Is Now Live

#129
post #63

Earlier quoted context omitted.

I run https://certsimple.com : we only do EV certificates, we're the fastest place to get an EV cert, we check as much as we can before you pay us a cent, and our application process is 80 seconds.

Yeah but still $234/yr for a certificate. While I appreciate what you're doing to make things more simple, that's pretty expensive. I can't wait until letsencrypt is done.

While I also look forward to letsencrypt being generally available, the fact your parent comment charges $234/yr for a cert is in response to:

> I'd actually pay more than I do now for SSL certs to get that kind of simplicity.

Re: Our First Certificate Is Now Live

#130

To be honest I had not heard of them till now, and I am a bit confused even after reading some of their site... So if the difficult part of being a CA (which I think is verifying that I, Paul Brian, own and control the rights to barlcaysbank.com and should have a certificate in that name) if that bit is either not done (!) or is reliant on donations to be able to afford it, is this going to work?

Yeah, verifying that "www.barclays.co.uk" is the correct URL for Barclays Bank PLC is what EV is for.

The other important role of a certificate is verifying that the server you're connected to is the correct one for the URL in the address bar. I may not know or care who "Hacker News" is supposed to belong to, but I do care that I'm connecting to the legit news.ycombinator.com, the same one I connected to yesterday, and that I'm not being Man-in-the-Middle'd.

The latter is what letsencrypt is for.

    |browser|- letsencrypt verifies -|server|- EV verifies -|organization|
Post reply on HN