5 ms·
WordPress.com illustrates an interesting challenge in supporting SSL if you allow people to use subdomains on your service: https://bestcrabrestaurantsinportla
by simonw 11y ago
WordPress.com illustrates an interesting challenge in supporting SSL if you allow people to use subdomains on your service:
https://bestcrabrestaurantsinportland.wordpress.com/ https://bestcrabrestaurantsinportland.wordpress.com/ works fine
https://www.bestcrabrestaurantsinportland.wordpress.com/ https://www.bestcrabrestaurantsinportland.wordpress.com/ displays a certificate warning
Unfortunately I don't think there's a good solution for this. Humans are gonna www- things.
- hayksaakian 11y agocan you get a second certificate? i'm not sure how the technology works, but since let's encrypt is free i think it could also be automated to solve this problem
- dsr_ 11y agoLE allows you to put many names in the same cert. Adding www is extremely simple.
- jquast 11y agoThere is a feature in X.509 for this, "Subject Alternative Names" to cover these alternate hostnames. https://en.wikipedia.org/wiki/SubjectAltName https://en.wikipedia.org/wiki/SubjectAltName http://wiki.cacert.org/FAQ/subjectAltName http://wiki.cacert.org/FAQ/subjectAltName https://www.openssl.org/docs/manmaster/apps/x509v3_config.html https://www.openssl.org/docs/manmaster/apps/x509v3_config.ht... Certificate authorities charge extra for it, of course they do. DigiCert brands this as "Multi-Domain (SAN) Certificate" and charges nearly $300/yr, while my choice provider, sslmate.com offers the same for $25/yr. And now $0 certificates with Let's Encrypt, I'm sad to see sslmate.com's business hurt, as they are the first to provide no-bullshit sysadmin-focused CLI tools to get the job done. I'm very wishful to see DigiCert.com and others like it go bankrupt, however. I don't see any reason why Honest Achmed's request to be a CA was denied by Mozilla, https://bugzilla.mozilla.org/show_bug.cgi?id=647959 https://bugzilla.mozilla.org/show_bug.cgi?id=647959 at least he is honest about his business model.
- pg_is_a_butt 11y agowhy not get a wildcard certificate for *.bestcrabrestaurantsinportland.wordpress.com? or just set the "Subject Alternative Name" for www in the cert... what is the problem?
- JoshTriplett 11y ago> Humans are gonna www- things. The same humans who incorrectly add "www." when not told to are also unlikely to add "https://" https://". So have the www. version redirect to the correct URL with HTTPS. For that matter, since certificates with Let's Encrypt support arbitrarily many SubjectAltName (SAN) values, you can include the www variant in the certificate, so that your redirect can use HTTPS and HSTS.
- XMPPwocky 11y agoBut then, if I'm MITMing you, I can just silently keep you on www, without SSL, without caring about HSTS or anything.
- iancarroll 11y agoIf WordPress enables (preloaded) HSTS, that would not matter.
- icebraining 11y agoI never understood why you can't get a wildcard cert for * . * .example.com. Then again, the whole concept of wildcart certs being priced differently is pure price segmentation, so that's to be expected.
- enraged_camel 11y agoIt's not price segmentation. You can encrypt X hosts with a wildcard cert, and X can be any number. So you basically buy encryption at a flat price, which can save you a LOT of money.
- icebraining 11y agoFair enough; maybe the term isn't correct. My point is that a wildcart cert is technically no different than a 'regular' cert, and the CA incurs in no extra cost, unlike with EV certs. The price difference is purely based on the fact that buyers who need wildcart certs tend to have larger budgets.
- deleted 11y ago[deleted]
- zanny 11y agoAnd then letsencrypt gives out free certs, but not wildcards, though their argument is more for securities sake.
- biot 11y agoIt's so people can't use one wildcard cert to have facebook.com.example.com and google.com.example.com, potentially tricking users.
- icebraining 11y agoI don't think that's a valid reason, because you can get a cert for * .com.example.com, hence you can have those domains.
- barsxl 11y agoThis happens with the https:// https:// vary rarely. The http:// http:// case happens more often. This is one of the complications in adding HSTS headers with includeSubDomains. Right now, the http:// http:// version works as expected, but if we added HSTS with includeSubDomains for "wordpress.com" those URLs would stop working and generate a SSL error. Somewhat related - if you have a mapped/custom domain on WordPress.com, even though we are strongly no-www[0] the "www" will work over HTTPS, assuming that DNS for the sub domain points to our servers[1] 0. http://no-www.org/ http://no-www.org/ 1. https://www.1912.me/ https://www.1912.me/