-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Client certificate chain is now sent #4894
Conversation
🎉 All Contributor License Agreements have been signed. Ready to merge. |
c77c7e4
to
ec21967
Compare
6cf59f0
to
d64f4f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed the non-test files, looking at tests.
src/rdkafka_cert.c
Outdated
if (sk_X509_num(ca) > 0) | ||
cert->chain = ca; | ||
else | ||
sk_X509_pop_free(cert->chain, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this need to be sk_X509_pop_free(ca,
instead? because cert->chain isn't assigned to yet.
07f402b
to
2fbf74c
Compare
…PEM format. Test that CA with untrusted chain fails authentication.
d64f4f8
to
f24ba97
Compare
04bd9b0
to
2f92f9f
Compare
2f92f9f
to
2af89bf
Compare
Hi @emasab, did you test with single cert in ssl.certificate.pem (where the CA is trusted on server)? having trouble setting up a client with an error bubbling up through this code change in 2.8 (2.6.1 works fine). I tried adding the CA after the cert but that failed too in 2.8 only.
|
when using
ssl.certificate.pem
orssl_certificate
orssl.keystore.location
.Without that, broker must explicitly add any intermediate certification
authority certificate to its truststore to be able to accept client
certificate.
Happens since: 1.x