I'm running lighttpd/1.4.28 (ssl) on Debian Squeeze. I just created a http://startssl.com certificate, I runs fine at all of my Browsers (Firefox, Chrome, Opera), but my users are reporting certificate-errors in Firefox. I already nailed it down to a failing of loading of the certificate chain:

Certificate at my Firefox: http://i.stack.imgur.com/moR5x.png
Certificate at others Firefox: http://i.stack.imgur.com/ZVoIu.png (Note the missing StartCOM-certificates here)

I followed this tutorial for embedding the certificate in my lighttpd: https://forum.startcom.org/viewtopic.php?t=719

The relevant parts of my lighttpd.conf look like this:

$SERVER["socket"] == ":443" {
        ssl.engine = "enable"
        ssl.ca-file = "/etc/lighttpd/certs/ca-bundle.pem"
        ssl.pemfile = "/etc/lighttpd/certs/www.bisaboard.crt"
}

ca-bundle.pem was created like this: cat ca.pem sub.class1.server.ca.pem > ca-bundle.pem
I grabbed the relevant files from here: http://www.startssl.com/certs/

www.bisaboard.crt was created like this: cat certificate.pem ssl.key > www.bisaboard.crt
Where certificate.pem is my StartSSL-Class1 Certificate and ssl.key my SSL-Root-Key.

Do you have any idea why the second Firefox does not correctly load the certificate-chain?

link|improve this question
feedback

1 Answer

Your webserver doesn't seem to present the intermediate certificates correctly, the reason it works in your own browser is probably because you've downloaded and installed them locally yourself.

Why don't you just download the ca bundle they already prepared for you at http://www.startssl.com/certs/ca-bundle.crt and use that for the ssl.ca-file option?

link|improve this answer
I tested that one as well. It does not work. And only some firefoxes are affected, I also have reports with working SSL. Additionally ONLY Firefox is affected, no other browsers. Edit: The random-SSL-Checkers out there in the web tell me my cert. would be valid: sslshopper.com/ssl-checker.html#hostname=www.bisaboard.de – TimWolla Jan 3 at 21:42
Funky stuff, my browser (Chrome 16 on OS X) doesn't recognize your issuer as trusted – Mathias R. Jessen Jan 3 at 21:51
At my Chrome 16.0.912.63 on Ubuntu Linux it works fine. Strange thing. – TimWolla Jan 3 at 22:02
Chain presentation looks good, see openssl s_client -connect www.bisaboard.de:443 -showcerts. @TimWolla Are you sure the failing browsers are properly trusting that StartCom root certificate? – Shane Madden Jan 3 at 22:02
@ShaneMadden There are less StartCom certificates than at my firefox, but at least the root-certificate is there: media.bisaboard.de/ssl-trusted.png <- That screenshot comes from the same firefox as the Windows-Firefox above. – TimWolla Jan 3 at 22:09
show 2 more comments
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.