acmed

456 Commits

13 Branches

28 Tags

2.4 MiB

Tree: 400cf6016f

Commit Graph

Author	SHA1	Message	Date
Rodolphe Breard	558fd63ab5	Rename post_operation_hook to post_operation_hooks	6 years ago
Rodolphe Breard	d0bf5bfc01	Add hook groups Some configurations may require to run the same bunch of hooks for several domains. In order to limit repetition, it is now possible to create a group that will reference to hooks or hook groups.	6 years ago
Rodolphe Breard	b3cbeaab4a	Allow to reuse a key pair instead of creating a new one at each renewal The default behavior of most ACME clients is to generate a new key pair at each renewal. While this choice is respectable and perfectly justified in most configuration, it is also quite incompatible with the use of HTTP Public Key Pinning (HPKP). Although HPKP is not wildly supported and sometimes deprecated, users wishing to use it should not be blocked. https://tools.ietf.org/html/rfc7469 https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning	6 years ago

Author

SHA1

Message

Date

Rodolphe Breard

558fd63ab5

Rename post_operation_hook to post_operation_hooks

6 years ago

Rodolphe Breard

d0bf5bfc01

Add hook groups

Some configurations may require to run the same bunch of hooks for
several domains. In order to limit repetition, it is now possible to
create a group that will reference to hooks or hook groups.

6 years ago

Rodolphe Breard

b3cbeaab4a

Allow to reuse a key pair instead of creating a new one at each renewal

The default behavior of most ACME clients is to generate a new key pair
at each renewal. While this choice is respectable and perfectly
justified in most configuration, it is also quite incompatible with the
use of HTTP Public Key Pinning (HPKP). Although HPKP is not wildly
supported and sometimes deprecated, users wishing to use it should not
be blocked.
https://tools.ietf.org/html/rfc7469
https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning

6 years ago

104 Commits (400cf6016f70b36c708ec6d9976af752408282f1)