mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
[PR #294] [MERGED] Basic implementation for private key rollover #792
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/294
Author: @crza
Created: 10/9/2016
Status: ✅ Merged
Merged: 10/17/2016
Merged by: @lukas2511
Base:
master← Head:keyrollover📝 Commits (7)
90c60e4initial commit for PRIVATE_KEY_ROLLOVERadb1c05fix if syntax5d96880rolloverkey without timestampsd85a1c8update example config: PRIVATE_KEY_ROLLOVER8b5a9c1rolloverkey creation logic updatedf7f00e1updated tests. untested.2770ccbadded cleanup for rolloverkeys: if disabled, delete privkey.roll.pem📊 Changes
3 files changed (+45 additions, -1 deletions)
View changed files
📝
dehydrated(+22 -1)📝
docs/examples/config(+3 -0)📝
test.sh(+20 -0)📄 Description
Hi Lukas!
Implementation of private key rollover
Currently uses $PRIVATE_KEY_ROLLOVER, should work for per-cert config.
To use:
PRIVATE_KEY_RENEW=yes
PRIVATE_KEY_ROLLOVER=yes
An extra private key is created on the first run.
If a rolloverkey and a private key exists, it swaps both.
If PRIVATE_KEY_ROLLOVER is disabled, rollover keys are deleted.
No changes to HOOK-api.
Hacked some CI-tests, but untested.
They should:
a) request a cert, create a private key [A], create a rollover key [B].
b) request a cert (forced), create a private key [C], swap rollover key [B] with private key [C]
c) Check if SHA256 Hash matches with [B](actual private key used on b) should match rollover key in a) )
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.