Skip to content

Intermediate CA trust in mTLS config #4557

Answered by MrAnno
adra78 asked this question in Q&A
Discussion options

You must be logged in to vote

If you find that Intermediate CA2 has also become the basis of trust, it may be because the other party sends that CA together with its own cert, and syslog-ng then validates it against your root CA, which is your real trust anchor.

If you want to trust "Intermediate CA1" only, you should make that your trust anchor, for example, by making it a root CA.

If that's not an option for you, the following syslog-ng options may also help you fine-tune your trust chain:

https://axoflow.com/docs/axosyslog-core/chapter-encrypted-transport-tls/tlsoptions/#tls-options-trusted-dn
https://axoflow.com/docs/axosyslog-core/chapter-encrypted-transport-tls/tlsoptions/#tls-options-trusted-keys

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by MrAnno
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants