3 ms·
Good news, you don't have to wonder how many GlobalSign issued, just look at the Excel file attached to the ticket and you can see all 113 of their "oopsies".
by 35fbe7d3d5b9 6y ago
Good news, you don't have to wonder how many GlobalSign issued, just look at the Excel file attached to the ticket and you can see all 113 of their "oopsies".
- tialaramex 6y agoNote that (opened in LibreOffice but I assume this isn't a document compat issue) the URLs all start https// but should begin https:// https:// instead. They're links into crt.sh which is a public view into the contents of the Certificate Transparency Logs, although they've also baked the certificate serial numbers into these links so if crt.sh goes away you can rewrite them as queries for any other system. It looks like an expected long tail, most of them were probably issued only days or weeks after the codes used should have expired (in 2017). What made this one jump out was the use of a 1024-bit RSA key. When it was really ordered that would be completely normal, but even in 2017 it would have been obviously prohibited, I have looked at a few of the other 112 and they're unextraordinary, typically 2048-bit RSA keys, likely originally ordered earlier in 2017. It would be useful (perhaps I will ask on m.d.s.policy) to know what the actual original order dates were for the 112 certificates in this list.
- bombcar 6y agoI assume the https// is intentional to prevent autolinking or similar (excel loves to make hyperlinks and not everyone knows how to beat it into submission).
- 35fbe7d3d5b9 6y ago> It would be useful (perhaps I will ask on m.d.s.policy) to know what the actual original order dates were for the 112 certificates in this list. It'd be really fascinating to compare that with WHOIS data for the domains. That might show other misissuances - certificates issued for non-registered domains.