-
Notifications
You must be signed in to change notification settings - Fork 113
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
v0.13: Generated cert signed by external CA cert returns cert that can't be validated against CA #261
Comments
If you have a chance, would be nice to run a |
@brocaar Thanks for the very detailed issue. I will try and investigate when I can. To confirm: you're using |
@cpu correct, please find the Cargo.toml for the example below: [dependencies]
rcgen = { version = "0.13", features = ["x509-parser"]}
pem = "3.0"
x509-parser = "0.16" |
@brocaar Thanks again for the detailed reproducer. It made this very easy to debug 🌠 PTAL at #262. When I run your reproducer with the
|
@cpu thank you for the quick feedback and fix 👍 |
This might be an error from my side, but after migrating to v0.13, I'm unable again to generate a client-certificate that can be validated against the CA certificate. The generated client-certificate does not have the same
X509v3 Authority Key Identifier
as the CA certificate.Most of the context is the same as #195, with the exception that this time when I load the CA certificate from an external file as
rcgen::Certificate
and then print it as PEM, theX509v3 Subject Key Identifier
is equal to the originalX509v3 Subject Key Identifier
of the CA certificate (that was what the #195 issue, where it would not preserve the original one).Summary
outCA.crt
and client-certificate toclientCert.crt
Validations:
rootCA.crt
X509v3 Authority Key Identifier
==outCA.crt
X509v3 Authority Key Identifier
rootCA.crt
X509v3 Authority Key Identifier
!=clientCert.crt
X509v3 Authority Key Identifier
rootCA.crt
contains:outCA.crt
contains:clientCert.crt
contains:Question
Is this a bug, or am I something missing in my migration from v0.12 to v0.13? /cc @cpu . Please find below my code under
main.rs
, as well therootCA.crt
androotCA.key
that I have been using for my testing (non-critical, only generated for testing this issue).Files
main.rs
rootCA.crt
rootCA.key
Example output
The text was updated successfully, but these errors were encountered: