1274850 - updated to 46.0.1 causes Secure Connection Failed security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE

Status: RESOLVED INCOMPLETE

(Core :: Security: PSM, defect)

Description

[Galen Thurber]

User Agent: Mozilla/5.0 (X11; Linux) AppleWebKit/538.15+ Midori/0.5

Steps to reproduce:

upgraded to 46.0.1
attempted to access several secure websites.



Actual results:

An error occurred during a connection to (any secured website) security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

Learn more…

Report errors like this to help Mozilla identify and block malicious sites


Expected results:

sites should have been reached.
firefox bug report should have been generated.
Notice that informed users how to report bug without using TLS.

Comment 1

[Dana Keeler (she/her) [:keeler]]

Some things to try:
* Do you see the same error when running with a new profile?
* What add-ons do you have installed?
* Are you connecting through a proxy?
* Are there any errors in the browser console? (Tools -> Web Developer -> Browser Console)
* Do you have an anti-virus program like Kaspersky running? (Might not be relevant if you're runnning Linux)
* Do you have any PKCS#11 modules loaded? (Preferences -> Advanced -> Certificates -> Security Devices)
* What is the output from running Firefox from a console with the environment variable NSPR_LOG_MODULES set to "pipnss:4,certverifier:5"?
* Are you running a version of Firefox downloaded from mozilla.org or one packaged and distributed by your OS? (Looks like Linux, if that field is correct.)

Comment 2

[Galen Thurber]

new profile, did not try
addons: xmarks, quickfox notes, adblock plus, ubuntu pack
console? did not try yet
AV? not installed Linux
security certs, none
from console have not tried yet.
version is ubuntu package updated via synaptic

The computer I am reporting on will be unavailable to me until around June 18th,
after that date I will debug it further

Comment 3

[Galen Thurber]

Still getting this in the browser window.
Firefox continues to freeze my Xubuntu for around 8 seconds and then allow me to control the mouse and GUI


Secure Connection Failed

An error occurred during a connection to www.google.com. security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

firefox -g
offers no additional information


firefox -ProfileManager
with a new profile did provide a successful TLS connection

Now what?

Comment 4

[Dana Keeler (she/her) [:keeler]]

Might be related to PKCS#11 modules - can you list the information in Preferences -> Advanced -> Certificates -> Security Devices?

Comment 5

[Galen Thurber]

During a backup I found the problem.

The upgrade firefox on 20160521
the upgrade changed the file permissions to root:root on these files
revocations.txt
search.json
search-metadata.json

I changed them back to user's usergroup and the error is gone

Comment 6

[Dana Keeler (she/her) [:keeler]]

Are those files in your profile or in some system directory? If the former, any idea why the upgrade changed the ownership to root:root? (Is that a Xubuntu bug?)

Comment 7

[Galen Thurber]

my profile.
No idea why ubuntu update would change the permissions to root:root
is it a package bug or ubuntu bug?

Comment 8

[Dana Keeler (she/her) [:keeler]]

This is looking like an ubuntu bug, but maybe :mgoodwin has an idea as to if it would be possible for Firefox code to have done this? (Basically, it looks like the ownership of revocations.txt in a profile directory got changed to root:root, and as a result the blocklist code couldn't read/write it.)

Comment 9

[Mark Goodwin [:mgoodwin]]

(In reply to David Keeler [:keeler] (use needinfo?) from comment #8)
> maybe :mgoodwin has an idea as to if
> it would be possible for Firefox code to have done this?

The only thing I can think of is for the Firefox process to have been started as root?

Comment 10

[Galen Thurber]

It was never run as root. I checked my bash history
Could it be the SSD entered a freeze mode, which it had been doing?

Comment 11

[Dana Keeler (she/her) [:keeler]]

I don't know enough about SSDs and freeze mode to know if that would cause the file ownership to have changed. I kind-of doubt it, though. Galen, is there anything further we can do here? It seems like this isn't an issue with Firefox.