Getting the certificate has an invalid signature error on one of my company's intranet sites.
Immediately after upgrading to FF35, I've lost the ability to access key parts of our intranet. I understand from other related forum questions that FF reps don't believe that typical users will encounter the problem of needing to access self-signed certificates over https. Here to tell you we do. The same issue keeps being posted on your forums regarding upgrades from FF31 onward (which at least allowed some user override). It looks like rather a lot of users have intranets that behave in the same way and would like to be able to use FF to access their own intranet sites. My company is highly unlikely to institute a massive security overhaul just to satisfy FF's sensitivities over the importance of this issue, especially when they have many other layers to protect themselves, so it's back to Chrome for me I guess.
Way to go.
All Replies (4)
hello, what kind of technical error code are you getting on the "connection untrusted" error page?
philipp said
hello, what kind of technical error code are you getting on the "connection untrusted" error page?
sec_error_bad_signature
there will be some fixes regarding this error code in firefox 36, but without access to the site in question it will be difficult to assess the problem and to know if those would apply in your case. therefore it would be best to report the issue to the it department of your company since they have more possibilities to investigate...
philipp said
there will be some fixes regarding this error code in firefox 36, but without access to the site in question it will be difficult to assess the problem and to know if those would apply in your case. therefore it would be best to report the issue to the it department of your company since they have more possibilities to investigate...
This won't happen. Our IT department is not going to spend time and money instituting changes because a new FF update blocks their intranet certification. I'll just be told to use Chrome or IE, which is what I'll do next. Might check back when update 36 is out.