3 ms·
I got the email. Here is the full text: This is an automatically generated email, please do not reply. Dear customer, As you are surely aware, the browser m
by nvr219 9y ago
I got the email. Here is the full text:
This is an automatically generated email, please do not reply.
Dear customer,
As you are surely aware, the browser makers distrusted StartCom around a year ago and therefore all the end entity certificates newly issued by StartCom are not trusted by default in browsers.
The browsers imposed some conditions in order for the certificates to be re-accepted. While StartCom believes that these conditions have been met, it appears there are still certain difficulties forthcoming. Considering this situation, the owners of StartCom have decided to terminate the company as a Certification Authority as mentioned in Startcom´s website.
StartCom will stop issuing new certificates starting from January 1st, 2018 and will provide only CRL and OCSP services for two more years.
StartCom would like to thank you for your support during this difficult time.
StartCom is contacting some other CAs to provide you with the certificates needed. In case you don´t want us to provide you an alternative, please, contact us at certmaster@startcomca.com
Please let us know if you need any further assistance with the transition process. We deeply apologize for any inconveniences that this may cause.
Best regards,
StartCom Certification Authority
- justinjlynn 9y agoAmusing that they couldn't get the encoding correct on their final email either.
- nneonneo 9y agoIt’s correct in the email I received. It’s a non-ascii apostrophe so I guess certain mail clients might not handle it correctly?
- nvr219 9y agoI copied and pasted from Outlook... probably Outlook's fault honestly.
- LukeShu 9y agoIn the email I received, it's a non-ASCII apostrophe encoded in UTF-8. The email headers say "Content-Type: text/html; charset=iso-8859-1", but then the HTML body says "<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>". Clients that give preference to the header will get it wrong. The full raw email: https://lukeshu.com/dump/startcom-email.txt https://lukeshu.com/dump/startcom-email.txt
- justinjlynn 9y agoeh, the header should match the body encoding regardless of meta tag; should it not?
- bound008 9y agoThis is more common than you think.
- LukeShu 9y agoYes, the header should match the body encoding, but it doesn't necessarily have to; that is in part what the <meta http-equiv> tag is for; it may be interpreted as saying "the value of header is potentially wrong, use this value instead" (of course, the thing says "http-equiv", and in an email, it isn't an HTTP header, it is a MIME header!) In HTML4/XHTML1, the <meta http-equiv> isn't meant to be interpreted by the user agent; the HTTP server is supposed to parse it and set the the HTTP header accordingly. Of course, the people writing the (X)HTML probably have a better idea of what encoding they're using than the people configuring the HTTP server, so it's common for user agents to allow <meta http-equiv> to override the actual header, as it allows more things to work "correctly" for users. But, strictly speaking, that is non-conforming. In (X)HTML5, that practice was codified, and the <meta http-equiv> tag is given preference over the actual headers (for a whitelist of allowed headers). So, which interpretation is "correct" depends on if it is HTML4/XHTML1 or (X)HTML5. Now, the MIME type of the email body said "text/html" which can be anything, and the body used the HTML5 doctype, but specified the XHTML1 xmlns. I'm honestly not sure which interpretation is correct in that case.
- cratermoon 9y ago