starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-07-22 12:58:34 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Support CLI arguments for contact e-mail address, EAB_KID and EAB_HMAC_KEY #642

New Issue
Open
opened 2025-12-29 01:28:07 +01:00 by adam · 0 comments
adam commented 2025-12-29 01:28:07 +01:00
Owner
Copy Link
Copy Source

Originally created by @GTAXL on GitHub (May 18, 2025).

Hello, a user may want to register to multiple CAs. You have to modify these parameters in the dehydrated config file, which are only really necessary during the registration process. EAB_KID and EAB_HMAC_KEY are unique for each CA account. I think it makes more sense as a CLI argument. Other ACME clients like acme.sh pass EAB as CLI arguments.

Contact e-mail: A user may want to use a different e-mail address for a particular CA. For example for Google Trust Services you'll probably want to use your gmail address that is tied to your Google Cloud account, and for Let's Encrypt a different e-mail.

EAB_KID and EAB_HMAC_KEY: These are fine in the config file if you just use one CA, but they are only really necessary one time, during registration. As I'm aware? If a user wishes to register with additional CAs, they'll have to keep manually updating the config file to reflect the new keys.

Originally created by @GTAXL on GitHub (May 18, 2025). Hello, a user may want to register to multiple CAs. You have to modify these parameters in the dehydrated config file, which are only really necessary during the registration process. EAB_KID and EAB_HMAC_KEY are unique for each CA account. I think it makes more sense as a CLI argument. Other ACME clients like acme.sh pass EAB as CLI arguments. Contact e-mail: A user may want to use a different e-mail address for a particular CA. For example for Google Trust Services you'll probably want to use your gmail address that is tied to your Google Cloud account, and for Let's Encrypt a different e-mail. EAB_KID and EAB_HMAC_KEY: These are fine in the config file if you just use one CA, but they are only really necessary one time, during registration. As I'm aware? If a user wishes to register with additional CAs, they'll have to keep manually updating the config file to reflect the new keys.
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#642