Bug 1428965 - Certificate trust errors with nss-pem 1.0.3
Summary: Certificate trust errors with nss-pem 1.0.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nss-pem
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-03 17:23 UTC by Adam Williamson
Modified: 2017-03-17 18:19 UTC (History)
1 user (show)

Fixed In Version: nss-pem-1.0.3-2.fc27 nss-pem-1.0.3-2.fc26 nss-pem-1.0.3-2.fc25 nss-pem-1.0.3-2.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-13 23:54:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
rpm -qa output (66.89 KB, text/plain)
2017-03-03 17:24 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2017-03-03 17:23:44 UTC
Since updating to nss-pem-1.0.3-1.fc25 from updates-testing, I have had problems with certificate trust errors. Here's two examples:

[adamw@xps13k bodhi (develop)]$ git pull
fatal: unable to access 'https://github.com/fedora-infra/bodhi.git/': Peer's certificate issuer has been marked as not trusted by the user.

[adamw@xps13k bodhi (develop)]$ curl https://fedorapeople.org/groups/qa/openqa-repos/openqa-testrepo-1.repo
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: https://curl.haxx.se/docs/sslcerts.html

After downgrading to nss-pem-1.0.2-2.fc25 , both these issues go away.

Attaching rpm -qa output as requested.

Comment 1 Adam Williamson 2017-03-03 17:24:13 UTC
Created attachment 1259610 [details]
rpm -qa output

Comment 2 Kamil Dudka 2017-03-06 12:27:40 UTC
Thanks!  This is caused by loading nss-pem into older nss package than it was built against.  I will introduce stricter dependency requirements in nss-pem.

Comment 4 Fedora Update System 2017-03-06 13:18:37 UTC
nss-pem-1.0.3-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9778e2d516

Comment 5 Fedora Update System 2017-03-06 13:18:43 UTC
nss-pem-1.0.3-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9778e2d516

Comment 6 Fedora Update System 2017-03-06 13:19:45 UTC
nss-pem-1.0.3-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e83e8f94b5

Comment 7 Fedora Update System 2017-03-06 13:19:50 UTC
nss-pem-1.0.3-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e83e8f94b5

Comment 8 Fedora Update System 2017-03-07 01:49:32 UTC
nss-pem-1.0.3-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9778e2d516

Comment 9 Fedora Update System 2017-03-07 17:52:22 UTC
nss-pem-1.0.3-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e83e8f94b5

Comment 10 Fedora Update System 2017-03-13 23:54:32 UTC
nss-pem-1.0.3-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2017-03-14 02:20:52 UTC
nss-pem-1.0.3-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2017-03-17 18:19:50 UTC
nss-pem-1.0.3-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.