Skip to content

Issues: pulp/pulp-certguard

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.

Sign up for GitHub

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

8 Open 9 Closed
8 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[DOC] where and how to generate client key&certificate for pulp Issue
#224 opened Feb 6, 2023 by TommyLike
1
CONTRIBUTING docs are out of date for how to test pulp_certguard Documentation Issue
#144 opened Jan 4, 2022 by pulpbot
Replace PyOpenSSL use with cryptography library from pypa Task
#143 opened Jan 4, 2022 by pulpbot
Update yum/dnf documentation on how .repo files can be configured to present a client cert and key Documentation High Task
#142 opened Jan 4, 2022 by pulpbot
1
Add a test to ensure FileRemote with client_cert and client_key configured can sync from a protected repository Task
#141 opened Jan 4, 2022 by pulpbot
Replace X509 artifact generation with trustme implementation Task
#140 opened Jan 4, 2022 by pulpbot
Add a test so that an expired client X509 Certificate should be denied Task
#139 opened Jan 4, 2022 by pulpbot
As a user I have path checking features for to the X.509 certguard Story
#138 opened Jan 4, 2022 by pulpbot
5
ProTip! Updated in the last three days: updated:>2024-11-22.