News for hackers. Stuff that matters.
Re:Our First Certificate Is Now Live by bracewel on Monday September 14, 2015 @06:06PM (#10217822)
The major problem with this is that the IETF validation working group hasn't come up with a definite procedure for deciding what the apex of a domain is, and how to validate control over all subdomains above it yet.
Re:Our First Certificate Is Now Live by dtech on Monday September 14, 2015 @06:10PM (#10217839)
Doesn't ownership of domain.tld also imply ownership of *.domain.tld?
Re:Our First Certificate Is Now Live by the_mitsuhiko on Monday September 14, 2015 @06:33PM (#10217959)
I don't think the owner of "co.uk" should have the power to issue certificates for everything below it.
Re:Our First Certificate Is Now Live by deathanatos on Monday September 14, 2015 @10:02PM (#10218612)
To make the original comment more precise, should not proving ownership of:

   <some domain>
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,

    <some domain>.<some public suffix>
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 by fidget on Tuesday September 15, 2015 @04:46AM (#10219592)
Because client support isn't there for nameConstraints. I really wish it was though.
Re:Our First Certificate Is Now Live by bracewel on Monday September 14, 2015 @06:16PM (#10217880)
That's the relatively simple case, but there are a number of corner cases that make the process much more complicated.

See https://github.com/letsencrypt/acme-spec/pull/97 for a discussion of why this was scraped from the ACME specification proposal.

Re:Our First Certificate Is Now Live by 0x0 on Monday September 14, 2015 @06:36PM (#10217967)
I don't get it. Whoever controls the base domain could always just replace the NS records and point any subdomain wherever.
Re:Our First Certificate Is Now Live by danellis on Monday September 14, 2015 @09:09PM (#10218438)
No? I thought I'd seen a list of them somewhere authoritative. Anyone know what I'm talking about?
Re:Our First Certificate Is Now Live by cel on Tuesday September 15, 2015 @01:02AM (#10219019)
Yes, the Public Suffix List: https://publicsuffix.org/
Re:Our First Certificate Is Now Live by danellis on Tuesday September 15, 2015 @02:13AM (#10219212)
That's definitely what I was thinking of, but it's not entirely suitable as a list of domains not to issue certificates for, unless you're happy to accept you won't be issuing certificates for domains like blogspot.com or flynn.io.
Re:Our First Certificate Is Now Live by ck2 on Monday September 14, 2015 @06:14PM (#10217863)
That's what Domain Validation (DV) is for and what most less-expensive wildcards use.