How do or don't multi-name wildcard certs work?
"John Levine" <[email protected]>
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Organization | Taughannock Networks |
| Message-ID | <[email protected]> |
One day I decided to build a content farm, which you can find at http://www.web.sp.am. Click on a few of the links and you will see that it consists of a very large set of similar pages with names like <a>.<b>.<c>.web.sp.am. On the theory that even stupid content deserves security, I'd like to move it to https. How do I do that? I got a cert for *.web.sp.am, but browsers dislike it, saying that the name in the cert doesn't match the domain name. I tried to get a cert for *.*.*.web.sp.am but Let's Encrypt, or at least the acme.sh client, says multiple wildcards aren't allowed. Any suggestions? (Beyond the obvious one to stop wasting my time?) Tnx, John _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix