starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-09-02 19:17:13 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

How to upgrade the key alogorithm #591

New Issue
Closed
opened 2025-12-29 01:27:36 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:27:36 +01:00
Owner
Copy Link
Copy Source

Originally created by @ghost on GitHub (Jan 5, 2023).

Hello!

I'm currently running with:

KEY_ALGO=prime256v1

I would like to upgrade to the secp384r1 algorithm, but it is not clear to me how to proceed. Do I just change my config KEY_ALGO to the new value and wait for auto-renewal? Do I need to change anything else in my infrastructure, for example Apache configuration?

I'd appreciate some help.

Thank you.

PS:
Maybe create an UPGRADE.md file with instructions, so people like me don't open issues in github?

Originally created by @ghost on GitHub (Jan 5, 2023). Hello! I'm currently running with: ``` KEY_ALGO=prime256v1 ``` I would like to upgrade to the `secp384r1` algorithm, but it is not clear to me how to proceed. Do I just change my config KEY_ALGO to the new value and wait for auto-renewal? Do I need to change anything else in my infrastructure, for example Apache configuration? I'd appreciate some help. Thank you. PS: Maybe create an `UPGRADE.md` file with instructions, so people like me don't open issues in github?
adam closed this issue 2025-12-29 01:27:36 +01:00
adam commented 2025-12-29 01:27:36 +01:00
Author
Owner
Copy Link
Copy Source

@lukas2511 commented on GitHub (Jan 19, 2023):

Normally you'd just need to wait for the next renewal or force a renewal.

If you have disabled PRIVATE_KEY_RENEW you'd of course need to re-enable it for this change. Also keep in mind that if PRIVATE_KEY_ROLLOVER is active the next key was already prepared with the old algorithm.

@lukas2511 commented on GitHub (Jan 19, 2023): Normally you'd just need to wait for the next renewal or force a renewal. If you have disabled `PRIVATE_KEY_RENEW` you'd of course need to re-enable it for this change. Also keep in mind that if `PRIVATE_KEY_ROLLOVER` is active the next key was already prepared with the old algorithm.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#591