-
Notifications
You must be signed in to change notification settings - Fork 9
add documentation for certificate-rotation #822
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
base: main
Are you sure you want to change the base?
Conversation
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on November 28. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
|
Deploy Preview Available Via |
|
To be reviewed and rebased after #755 lands, and once we are done with the platform release tasks. |
| openssl req -x509 -newkey rsa:4096 \ | ||
| -keyout /tmp/new-key.pem \ | ||
| -out /tmp/new-cert.pem \ | ||
| -days 365 -nodes \ | ||
| -subj "/CN=your-hostname/O=YourOrganization" |
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.
Shouldn't we recommend ed25519?
Rather use the Starter to generate certificates? We include it in ArangoDB packages
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.
Yes Simran, we can use the Starter as well. I’m not fully sure about recommending ED25519 for TLS certificates.
For the documentation, I followed the customer’s requirement - since they generated their own certificates, I used OpenSSL as the example.
@jwierzbo, can you please confirm?
Description
Upstream PRs