This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

FF33 doesn't like our internal SSL certificates.

ChrisKarel
ChrisKarel
more options

Updating FireFox to version 33 breaks SSL connectivity with certificates signed by our company's internal CAs. As of the latest update, we get the following error message with no method of override:

An error occurred during a connection to www.google.com. security library: improperly formatted DER-encoded message. (Error code: sec_error_bad_der)

I assume the problem stems from the new mozilla::pkix certificate validation. The sec_error_bad_der seems to indicate there's a parsing issue with the certificate itself.

These certificates work fine in FF <32, Chrome, and MS IE. But I recognize there may be something subtly wrong with these certs that should be corrected. However, FireFox doesn't actually give any useful information to help troubleshoot this. What options are available to discover what exactly FF is finding so broken about these?

Updating FireFox to version 33 breaks SSL connectivity with certificates signed by our company's internal CAs. As of the latest update, we get the following error message with no method of override: An error occurred during a connection to www.google.com. security library: improperly formatted DER-encoded message. (Error code: sec_error_bad_der) I assume the problem stems from the new mozilla::pkix certificate validation. The sec_error_bad_der seems to indicate there's a parsing issue with the certificate itself. These certificates work fine in FF <32, Chrome, and MS IE. But I recognize there may be something subtly wrong with these certs that should be corrected. However, FireFox doesn't actually give any useful information to help troubleshoot this. What options are available to discover what exactly FF is finding so broken about these?

Toate răspunsurile (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Sorry to put this work on you, but I don't understand many of the comments in these bugs about issues with the signing certificate. You probably are in a better position to understand them:

https://www.google.com/search?q=sec_error_bad_der+site:bugzilla.mozilla.org&tbs=qdr:y