Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tialaramex
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
1775 ms
·
12061.
▲
by
tialaramex
10y ago
Not clear to me what the problem is with your current setup? Let's Encrypt is happy to issue for (almost) any Fully Qualified Domain Name in the Internet DNS, and no-ip.org is on the Public Suffix List, so you won't be sharing you
12062.
▲
by
tialaramex
10y ago
First up I will nitpick. The certificates were issued from an Intermediate, "Symantec Class 3 Secure Server CA - G4" not from a root. Hopefully Symantec keeps all the actual roots safely physically off-line in smart cards or simil
12063.
▲
by
tialaramex
10y ago
It's not about these particular certificates, it's about the fact that Symantec issued obviously bogus certificates at all, and then that they either didn't catch it or they caught it and decided to try not to tell us about i
12064.
▲
by
tialaramex
10y ago
www.airbnb.com and other sites aren't affected, so it seems like this will mostly affect people who specifically type in https://airbnb.com/
12065.
▲
by
tialaramex
10y ago
The ACME server absolutely does generate the end entity certificates for their subscribers (e.g. a certificate on your web server). Code which does this is part of Boulder, the Let's Encrypt implementation of an ACME server so you can
12066.
▲
by
tialaramex
10y ago
Almost. The way you've described only works if the ACME user also has access to the private key for the CSR. But that isn't true if you're using CSRs from some appliance you bought which doesn't let you change or view it
12067.
▲
by
tialaramex
10y ago
The first part of the story definitely checks out https://crt.sh/?id=29236482 This certificate absolutely was revoked by GoDaddy However, that certificate is _still_ revoked right now. A _new_ certificate for the same names
12068.
▲
by
tialaramex
10y ago
What you wrote about not needing "to generate certificates" is quite wrong, though I suppose I get what made you think this. ACME uses public key cryptography in (at least) three separate places, the keys pairs are different in ea
12069.
▲
by
tialaramex
10y ago
So, the way X.509 works, certificates aren't signed by a particular other certificate, but by a named Issuer and private key. This particular Issuer, "Google Internet Authority G2" has both an older SHA-1 certificate (which e
12070.
▲
by
tialaramex
10y ago
No. CAA is an instruction to Certificate Authorities, not an instruction to clients. Let's Encrypt obeys CAA, if you try to validate for a domain which has a CAA record saying e.g. "Only Symantec may issue for this domain", L
12071.
▲
by
tialaramex
10y ago
(Not for ygjb-dupe's interest as I'm sure they know already, but for the sake of the thread) To slightly expand, getting trusted by the key trust stores (laughably pretending to each represent a "Web browser" at CA/
12072.
▲
by
tialaramex
10y ago
Probably someone needs to ask IANA to do so. As far as I know (and I'm happy to learn otherwise) the first mention of .well-known/pki-validation was Ballot 169 https://cabforum.org/2016/08/05/ballot-