hyperrot.blogg.se

1. #Deploying ssl certificates to mozilla firefox esr update#
2. #Deploying ssl certificates to mozilla firefox esr download#

Even more strange, not a single word from openSuse to explain the issue or suggest a workaroundīojanas far as I can tell you're mixing Firefox packages if you're going to use Firefox 57 from the Mozilla repo you need to do a full vendor change to that repo as it would seam you have mozilla-nss 3.28.6 for esr from the update repo and you should be using mozilla-nss 3.34.1 from the mozilla repo Strange however, that no description or questions related to similar problems can be found on the net. By all means, the openSuse is to be blamed. However, if FF57 is downloaded from Mozilla site all certificates work excellent as they should. Same certificates issue with FF57 (from opensuse repository) on Leap 42.3.

mozilla folder from backup, in order to have back previous addons etc.). So I can't do any other thing but revert my Firefox to official line of ESR versions (currently 52.4) (and getting back the. There are pretty low chances for anyone else to be able to check similar conditions, other than the exact same site where my problem arise, with me sending the specific FILE.p12 certificate file to import into their browser - and this is not quite feasible.

So, it definitely seems to be some other specific setting, probably compiled inside the browser on Opensuse side (?) I can't find any other justification for this. mozilla folder and force it create a new one - again it's not working !Īs far as I can check, specific options related to PKI in about :config look identical between version that do and do not work (either on my computer, and on other computers that do work OK (windows laptops)). started Opensuse 56 after removing the previous. started again stock version of Firefox 56 - it does work OK with that certificate ! mozilla created by above stock version - it does not work ! started OpenSuse version of Firefox 56 (from repository "Mozilla"), on the same folder. started Firefox as if first run on computer from unzip-ed folder from stock version (downloaded from Mozilla site) - it works good with that certificate (of course, first I installed it on Firefox) moved folder ~/.mozilla to a backup location Or on the contrary, it has something added in the settings that I could revert in order to make it work ?Īs far as I can find out myself through a few testing, it definitely seems to be OpenSuse specific issue. Is there any explanation why the Firefox 56 from Leap 42.2 repositories refuses to load this certificate (despite it using that old algorithm) ?

#Deploying ssl certificates to mozilla firefox esr download#

With older ESR versions from official update repo it worked very well.Īlso, version Firefox 56 on a Windows system loads well the same certificate.Īlso, again, if I download the version 56 from Mozilla site, and use it on my Leap42.2 system, it loads well the certificate ! (of course, before trying this manoeuvre, I did make a backup of ~/.mozilla folder and started this version as if it were first time ever on my computer). I can't find a reason why I can't login now, with Firefox 56 (version 56.0.1-1.1). it just uses old SHA1 algorithms (yeah, government owned site, what can I say.) Unfortunatelly I was stuck on this error when trying to acces some particular site that uses SSL certifs: "Error code: SSL_ERROR_HANDSHAKE_FAILURE_ALERT"Ĭertificate is officially obtained from that site (paid, of course), so it's accurate/trustworthy. I used the particular repository "Mozilla" ( ) On my Leap 42.2 (for personal reasons I did not switched to 42.3) I wanted to use Firefox latest version, and not the current line of versions ESR that official repositories are offering.