-
Notifications
You must be signed in to change notification settings - Fork 579
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
Doc: Distributed Monitoring: add section "External CA/PKI" #9825
Conversation
ba89e5a
to
922dc11
Compare
da9e786
to
5ee4076
Compare
5ee4076
to
0e239eb
Compare
FWIW, we've already written this under https://icinga.com/solutions/monitoring-and-security/
|
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.
In general, I am happy with this addition to the docs. There are only two points left (next to my inline comment):
- Please expand the contracted forms of the words, like "don't" to "do not".
- This may be optional, but might help. What about actual commands showing how to use an external CA? At the moment, this section is on a very theoretical level. If you say this theoretical approach is enough, I am fine with this as well.
I could do it, but what for? Also, see e.g:
And that's perfect. We're not responsible for what we don't provide. :-)
|
0e239eb
to
25fb3c8
Compare
The following already works: * Custom key sizes, e.g. 2048 bits * Custom key types, e.g. ECC * Multiple trusted root CAs in `/var/lib/icinga2/certs/ca.crt` * Different root CAs per cluster subtree, as long as each node trusts the issuers of the certificates of all nodes it's directly connected to * Any number of intermediate CAs
25fb3c8
to
5011752
Compare
The following already works:
/var/lib/icinga2/certs/ca.crt
refs #9798
refs #7323