Project

Profile

Help

Story #789

closed

As a user, I can manage Nectar's trust through the system Certificate Authority store by default

Added by rbarlow about 9 years ago. Updated about 5 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Target Release - Nectar:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Quarter:

Description

Currently, python-requests ships with its own Certificate Authority store, at /usr/lib/python<version>/site-packages/requests/cacert.pem. This means that users cannot manage the certificate store that is used to verify remote Nectar connections using ordinary system management tools, as they might expect.

We should alter Nectar so that it configures python-requests to use the system certificate authority store by default.

Document this in release notes, including the small risk associated with changing the CA bundle.


Related issues

Related to Pulp - Issue #816: python-requests bundles libraries and CA certificates that should be separateCLOSED - CURRENTRELEASEjcline@redhat.comActions

Also available in: Atom PDF