Changed handling certificates for NSS and updated dependencies #130
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant Issues/Pull Requests (if applicable)
n/a
Details
The handling of certificates by the NSS library has been changed for Fedora and Rocky Linux.
When loading certificates, it is assumed that the server and client certificates have been converted to PKCS#12 certificates and loaded into NSSDB.
It is also assumed that the CA certificate is also loaded into NSSDB.
In CentOS 7,
libnsspem.soexists, but other than that, PEM files cannot be directly imported into NSSDB, so it is handled this way.Accordingly,
chmpxnssutil.shhas been updated and included in the RPM package.This tool is available for importing PEM certificates into NSSDB on Fedora and Rocky Linux.
And it also updated the versions of dependent packages.