We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cryptography
Author: @bmbouter (bmbouter)
Redmine Issue: 7484, https://pulp.plan.io/issues/7484
library to use: https://pypi.org/project/cryptography/
The code itself uses PyOpenssl in two areas:
Validation a certificate is in PEM format here
Ensuring a certificate is unexpired here
Ensuring a client certificate is signed by the CA certificate here
The load_pem_x509_certificate call expects a PEM encoded cert (not DNR) so we can test this provides validation at instantiation time.
load_pem_x509_certificate
We can probably manually check a valid certificate's usng the `Certificate.not_valid_after attribute against the current UTC time.
I do not see how to validate that a valid PEM certificate was signed by another valid PEM certificate.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Author: @bmbouter (bmbouter)
Redmine Issue: 7484, https://pulp.plan.io/issues/7484
library to use: https://pypi.org/project/cryptography/
Current usage:
The code itself uses PyOpenssl in two areas:
Validation a certificate is in PEM format here
Ensuring a certificate is unexpired here
Ensuring a client certificate is signed by the CA certificate here
Replacement calls in
cryptography
The
load_pem_x509_certificate
call expects a PEM encoded cert (not DNR) so we can test this provides validation at instantiation time.We can probably manually check a valid certificate's usng the `Certificate.not_valid_after attribute against the current UTC time.
I do not see how to validate that a valid PEM certificate was signed by another valid PEM certificate.
The text was updated successfully, but these errors were encountered: