Comment # 9 on bug 1071298 from Moritz Duge

(In reply to Wolfgang Rosenauer from comment #7)
> I now tested Firefox from mozilla built for 42.3 on Tumbleweed and it seems
> to work. It says "standby" but I wasn't able to test with a real client
> certificate.
> 
> The CACert testcase still fails for me but this might have different reasons
> still.

I also tested Firefox from mozilla-42.3 on
openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20180106-Media.iso.
And I was able to reproduce the error with this setup!



Actually it was a little tricky to install the current RPMs from the
mozilla-42.3 repo, because they have exactly the same version numbers as the
current Tumbleweed RPMs.

Trick:
1. First install Firefox from standard repos to pull all dependencies
2. then disable all Tumbleweed standard repos
3. then reinstall all packages from the mozilla-42.3 repo.

So do you think this might has been the reason why Firefox from mozilla-42.3
seemed to work for you on Tumbleweed?
Alternatively you may repeat your test with a real certificate installed. Else
Firefox might not behave as needed to reproduce this bug.



After 1. I did a short test with the Tumbleweed standard Firefox and x509
authentication worked fine!



I also tested Firefox-57 from the Tumbleweed repo on my openSUSE-42.3 system
(had to install updated libz1 from Tumbleweed repo too). And then x509
authentication works.



(In reply to Wolfgang Rosenauer from comment #8)
> So in case you are able to test a similar thing (42.3 packages on TW) you
> could help to verify if it really works. If it does there is only a runtime
> difference. While I currently would have no idea what that might be.

Concluding my test results I'm pretty sure this is a problem when building
Firefox-57 in the mozilla repo against openSUSE-42.3. Mostly because installing
the mozilla-Tumbleweed Firefox-57 instead of the mozilla-42.3 Firefox-57 on
openSUSE-42.3 solves the bug.