Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate
by pilom on Monday November 14, 2016 @06:33PM
(#12954319)
We use wildcard certs for a number of domains to support affiliate subdomains. So affiliate.example.com and affiliate2.example.com are all served by the same servers and thus all need to validate with one cert.
[ Parent
| on HN ]
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate
by duaneb on Monday November 14, 2016 @06:48PM
(#12954391)
You can use SAN certificates to avoid wildcards while still validating for a number of domains.
They don't even need to be subdomains.
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate
by Johnny555 on Monday November 14, 2016 @07:06PM
(#12954516)
There's a limit to how many SAN's you can fit in one cert. There is apparently no defined upper bound, but dependent on the client's implementation. 25 - 100 names seems to be the common limit supported by most registrars.
In the parent poster's case, it sounds like a good use case for a wildcard cert. They may have thousands of affiliates, and may not know all of the affiliates ahead of time, so with a SAN cert, would need to reissue the certificate each time a new affiliate signs up.
https://community.letsencrypt.org/t/subjectaltname-certifica...
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate
by duaneb on Monday November 14, 2016 @08:37PM
(#12954925)
Oh, I completely agree—I maintain a SAN and it's a royal pain in the ass.
But there are options, and a SAN has lower risk if your key is leaked (only the enumerated domains will validate).