4 ms·

Thanks for your reply. Ubuntu Firefox, Android Chrome... scary warnings pretty much everywhere. It'd be surprising if all these clients didn't have StartCom's r

Thanks for your reply. Ubuntu Firefox, Android Chrome... scary warnings pretty much everywhere. It'd be surprising if all these clients didn't have StartCom's root certificate. If you don't mind, how did you set up your /etc/ssl/server.crt file?

phaer 12y ago
Are you sure they have the same root certificate? About a month ago, I ran in some problems because I got a new certificate from RapidSSL which had been signed by their new-ish SHA256 certificate but older clients (~3 years old browsers) had only RapidSSLs old root certificate installed.
- ezequiel-garzon 12y ago
  Thanks for answering. I'm not sure, but wouldn't this be a widespread issue, given the popularity (read free as in beer) of StartCom certificates? I'm pretty sure I'm doing something wrong.
  - phaer 12y ago
    If you are using Firefox: click on the padlock icon -> "more information" -> "view certificate" and then on the "details" tab. If you check "certificate signature algorithm" for each of the 3 certificates, you'll see that the root certificate as well as your own one are using SHA256 but that the intermediate certificate is using SHA1. You need to bundle the right intermediate certificate which you can find, together with additional information, on https://shaaaaaaaaaaaaa.com/ https://shaaaaaaaaaaaaa.com/
    - ezequiel-garzon 12y ago
      Thanks a lot! I will look into tha. As far as I can tell StartCom didn't give me a choice in that regar. Thanks for pointing me to that site. (I'd say it beats Slashdot in difficulty when you have to pass it on verbally!)
- deleted 12y ago
  [deleted]