4 ms·
The story links to an "https" URL, which is odd for several reasons, 1. Since when does a blog need to be secure? 2. The certificate is issued to "*.wordpress
by tantalor 14y ago
The story links to an "https" URL, which is odd for several reasons,
1. Since when does a blog need to be secure?
2. The certificate is issued to "*.wordpress.com", which is useless. Each subdomain under wordpress.com should have a distinct certificate since they have a distinct author. The certificate should be specific to the author, not the host.
- I realize it is not realistic to assign unique IP addresses to each wordpress.com subdomain. I just don't like it.
3. The page loads insecure content from gravatar.com and googleservices.com, which throws up annoying errors.
- 46Bit 14y agoMixing insecure content makes it stupid, but as someone who uses https on my blog, it comes down to why not to use it. For the time being there's no reason, especially when Gandi give free certificates with a domain. The one quirk is that I'll always have to have something to redirect to unsecured should traffic ever get so high it becomes an issue. Although I certainly don't expect that any time soon.
- ajross 14y agoCertificates don't go with "authors", they go with domains. They are only (!) a promise that some grown up at a cert factory decided that the admin of the host you are connecting to was the proper owner of that domain. Now sure, there might be value in having per-subdomain certs in wordpress (though that would be rather complicated for wordpress to administer). But there's nothing wrong with that wildcard cert -- it provides proof that you've reached a blog hosted at wordpress, and not a MitM ready to lift your account password when you try to leave a comment.
- mwilcox 14y agoSorry, this was my fault. I have a Chrome extension that forces everything to https, and forgot to remove it when I submitted the link.