Firefox ESR 115.2.0 Warning: Potential Security Risk Ahead - No advanced Button
Hello Guys,
in our network we have several Fritzbox Routers which we remote administrate. If we connect to the routers with Firefox V115.2.0 we get a warning message - because it´s a Fritzbox self-signed certificate and cannot be validated. No Problem - everything okay with the message. But in Firefox 115.2.0 there is no advanced button that lets you go futher to connect to the website. With Version 102.14.0 ESR the advanced button is there. The webinterface works fine with Edge and Chrome (with warning but with advanced button to continue)
Is this a bug?
Best Regards, Michael
การตอบกลับทั้งหมด (5)
Do you see the same thing when you go to https://self-signed.badssl.com/?
yes, same thing if i open https://self-signed.badssl.com/? with version 115.2.0 - no advanced button to continue. if i open the site with 102.14.0 the advanced button is there.
I'm at a loss for that one. IS there anything set in about:policies? Does it happen with a new profile?
yeah, we did some easy settings with policies. But nothing really special - and these settings are not touched since a few versions.
And yes - fresh Windows Userprofile, fresh Firefox Profile - the advanced Button is not displayed with 115.2.0 in our Enterprise Environment.
Today we installed 115.2.0 ESR on a private computer (non domain joined) and connect to the Webinterface of the Router, from outside of our enterprise network. This works well and the advanced Button is displayed!
The difference between the private computer and our enterprise environment - we use a proxy server in our enterprise environment. (But all other Browser and Firefox Version 102.14 also use the same proxy server, and it´s working.)
My colleague tested some Versions of the non ESR releases. Their are also some Versions with this behavior, but 117 works.
Perhaps something has changed in terms of communication in conjunction with a proxy server? The whole thing doesn't explain itself to me at all at the moment
Can you disable the proxy in the enterprise environment and see if that changes things?
Are there any errors on the JS console?
I looked through the code to see what could cause this and I can't find anything.
I'd be more than happy to walk through a debug session to try to figure it out.