-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing a ca chain only imports the first certificate #5162
Comments
Related downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1878808 |
Bug Description: Nss can't import pem chain files which can confuse users why they have missing certificates when they try to import a chain. Fix Description: Error out on chain files in any of the import paths since they are ambiguous. fixes: 389ds#5162 Author: William Brown <william@blackhats.net.au> Review by: ???
Bug Description: Nss can't import pem chain files which can confuse users why they have missing certificates when they try to import a chain. Fix Description: Error out on chain files in any of the import paths since they are ambiguous. fixes: #5162 Author: William Brown <william@blackhats.net.au> Review by: @droideck
Bug Description: Nss can't import pem chain files which can confuse users why they have missing certificates when they try to import a chain. Fix Description: Error out on chain files in any of the import paths since they are ambiguous. fixes: 389ds#5162 Author: William Brown <william@blackhats.net.au> Review by: @droideck
Bug Description: Nss can't import pem chain files which can confuse users why they have missing certificates when they try to import a chain. Fix Description: Error out on chain files in any of the import paths since they are ambiguous. fixes: #5162 Author: William Brown <william@blackhats.net.au> Review by: @droideck
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: 389ds#5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Parse PEM file and add each CA cert separately. Fixed some PEP8 errors. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: 389ds#5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
Description: Incorrectly added "required=True" to positional arg nickname when adding ca-cert. relates: #5162 Reviewed by: ?
after this commit (at least, in the version 2.0, commit 98aa09d) the file security.py uses the function "log.info()". The result is that it is impossible to set some (maybe even any?) security property:
It's probably a mistype in the argument name of the functions "def _security_generic_get(inst, basedn, logs, args, attrs_map):" and "def _security_generic_set(inst, basedn, logs, args, attrs_map):". The argument name "logs" should be replaced by "log"?
|
The 'log' typo is now fixed. See issue 5539 |
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: 389ds#5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: 389ds#5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: Verify that when importing a certificate that is the correct type. Also cleanup temporary certs that are created when processing a bundle of certs in a PEM file. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: 389ds#5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: #5162 Reviewed by: spichugi(Thanks!)
Description: With recent changes to certificate validation the error message has changed and the CI needs to be updated. relates: #5162 Reviewed by: spichugi(Thanks!)
ba7ad9a4f..ee1e525b0 389-ds-base-1.4.3 -> 389-ds-base-1.4.3 |
A ca chain pem file is just a series of pem certs concatinated. NSS of course, when presented with a chain file will only import the first certificate, and will silently ignore the rest.
This can create user confusion who expect to be able to import a chain file.
While we can't fix NSS, we CAN fix dsctl instance tls import commands such that when a chain file is presented we can inform the user they need to split it and import the components individually.
The text was updated successfully, but these errors were encountered: