Invalid SSL caused by outdated nss-updatedb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nss-updatedb (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've done some research regarding this issue and the result pointed to an outdated nss-updatedb database.
The expected behaviour:
Green padlock on SSL generated using SHA-2 on Chrome.
The problem:
Using Chrome, the browser display invalid SSL (red lock and crossed https). When clicking on details, it says that the connection is secure and encrypted. The certificate is SHA-2, and as far as I understand the problem occurs in Chrome when the certificate was generated using SHA-1, but this is not the case.
I had this problem on Mint, but as soon as I've installed nss-updatedb the SSL was valid again.
Now on Ubuntu 15.04, the problem is back (didn't happen on 14.04).
Description: Ubuntu 15.04
Release: 15.04
nss-updatedb:
Installed: 10-3
Candidate: 10-3
Version table:
*** 10-3 0
500 http://
100 /var/lib/