3 ms·
The cert includes a wildcard for *.google, which Firefox rejects because it's a wildcard on a top level domain. I can't really tell who's right here from the sp
by rockdoe 11y ago
The cert includes a wildcard for *.google, which Firefox rejects because it's a wildcard on a top level domain. I can't really tell who's right here from the specs.
https://bugzilla.mozilla.org/show_bug.cgi?id=1169149 https://bugzilla.mozilla.org/show_bug.cgi?id=1169149
- stygiansonic 11y agoGood catch! The addition is for the new .google TLD. Looks like the Chromium source code had some "protection" against this, at least at one point in time: http://security.stackexchange.com/questions/6873/can-a-wildcard-ssl-certificate-be-issued-for-a-second-level-domain http://security.stackexchange.com/questions/6873/can-a-wildc... It appears that the specification (RFC 2818?) doesn't specify what is acceptable with regards to allowed wildcard certificates - leaving the various implementations to decide what is "too risky" for themselves.