Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: TLSA records #16

Open
yan-foto opened this issue Jan 22, 2022 · 2 comments
Open

Feature request: TLSA records #16

yan-foto opened this issue Jan 22, 2022 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@yan-foto
Copy link

I was wondering if it's possible to also update TLSA records after a certificate is fetched?

@nils-wisiol
Copy link
Contributor

Currently, TLSA updates need to be done manually after obtaining the certificate. Over at desec-io/desec-stack#513, there is some effort to auto-generate TLSA records from certificates. If this ever becomes available through the deSEC API, we would still have to figure out if the certbot plugin interface provides functions that are called after successfully obtaining a certificate.

We need to proceed with caution, though, as record updates need to be carefully coordinated with the actual certificate switch at the web server. I believe https://github.com/raforg/danectl implements an appropriate workflow for this.

@nils-wisiol nils-wisiol added enhancement New feature or request help wanted Extra attention is needed labels Jan 24, 2022
@yan-foto
Copy link
Author

That's a very good point. I had the impression that certbot provides some post-fetch hooks for the plugins: doesn't the nginx plugin update config files after certs are issued?

I'll give it a look as soon as I get some free time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants