Skip to content

ceremony: accept path to pkcs11 creds file#8626

Open
maen-bn wants to merge 2 commits intoletsencrypt:mainfrom
maen-bn:ceremony-accept-path-to-pkcs11-cred-file
Open

ceremony: accept path to pkcs11 creds file#8626
maen-bn wants to merge 2 commits intoletsencrypt:mainfrom
maen-bn:ceremony-accept-path-to-pkcs11-cred-file

Conversation

@maen-bn
Copy link
Contributor

@maen-bn maen-bn commented Feb 12, 2026

Only supported with the intermediate config and will overwrite any of the pkcs11 signing config values in the yaml file if the creds file path is provided and successfully loaded and parsed

Resolves #8377

@maen-bn maen-bn requested a review from a team as a code owner February 12, 2026 11:53
only supported with the intermediate config and will overwrite any of
the pkcs11 signing config values in the yaml file if the creds file
path is provided and successfully loaded and parsed
@maen-bn maen-bn force-pushed the ceremony-accept-path-to-pkcs11-cred-file branch from 850f0a9 to faec37b Compare February 12, 2026 13:18
@maen-bn maen-bn force-pushed the ceremony-accept-path-to-pkcs11-cred-file branch from faec37b to 2ec6c76 Compare February 12, 2026 13:19
Copy link
Contributor

@aarongable aarongable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Three high-level thoughts:

  1. This also needs to work uniformly across all other applicable ceremony types, like generating CRLs and cross-certs.
  2. Instead of having the CredentialsPath override the Module/PIN/etc, the .validate() method should return an error if both are supplied.
  3. We need to think critically about how this interacts with the root ceremony and intermediate keygen ceremony, which both use a PKCS11KeyGenConfig, which has many of the same fields. I'm truly not sure of the best solution here, and we probably shouldn't proceed until we have thought it through. I'll put my fuller thoughts on that question in the bug, where it's a bit more visible for posterity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ceremony: accept path to pkcs11 creds file

2 participants