Live data from Hacker News

Termination of StartCom business

startcomca.com

21–30 of 47 posts

Re: Termination of StartCom business

#23
post #11
post #7

Earlier quoted context omitted.

Maybe you get a shiny new Turk Trust cert in exchange. Who knows.

I have no idea if 'Turk Trust' is even a real CA or if you made up the name in jest. I'm honestly scared to Google it and find out, in slight fear of finding out that is an actual CA. (Not to get too political here, but given Turkey's current government, I'm not sure how anyone in their right mind would 1- trust them to say or do _anything_, and 2- trust SSL encryption certs coming out of there)

It's real:

https://bugzilla.mozilla.org/show_bug.cgi?id=1007683

Re: Termination of StartCom business

#24
post #16

Earlier quoted context omitted.

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…

Amusing that they couldn't get the encoding correct on their final email either.

It’s correct in the email I received. It’s a non-ascii apostrophe so I guess certain mail clients might not handle it correctly?

Re: Termination of StartCom business

#26
post #16

Earlier quoted context omitted.

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…

Amusing that they couldn't get the encoding correct on their final email either.

In 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 "". Clients that give preference to the header will get it wrong.

The full raw email: https://lukeshu.com/dump/startcom-email.txt

Re: Termination of StartCom business

#28
post #26

Earlier quoted context omitted.

Amusing that they couldn't get the encoding correct on their final email either.

In 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 " ". Clients that give preference to the header will get it wrong. The full raw email: https://lukeshu.com/dump/startcom-email.txt

eh, the header should match the body encoding regardless of meta tag; should it not?

Re: Termination of StartCom business

#29
post #22

Even though it ended badly they were the first to offer free certificates.

I think dealers give away coke at the onset, no?

I've met a lot of dealers and I am still waiting for my free coke...

Free certificates were free, no trick. Of course they recommended their paid offer, but there is nothing wrong with that.

You may argue that StartSSL turned some webmasters into https addicts but it is not exactly a bad thing isn't it? Remember that Let's Encrypt didn't exist back then.

Re: Termination of StartCom business

#30
post #26

Earlier quoted context omitted.

In 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 " ". Clients that give preference to the header will get it wrong. The full raw email: https://lukeshu.com/dump/startcom-email.txt

eh, the header should match the body encoding regardless of meta tag; should it not?

This is more common than you think.
Post reply on HN