Originally created by @andreasschulze on GitHub (Dec 12, 2018).
When using ACME to issue certificates for Mailservers, one may want to publish TLSA-Records too.
The general timeline would be:
generate a new private key + req
issue new cert
calculate the TLSA-Record data (TLSA Mode 3 3 1)
put these data into DNS
make sure, the published TLSA Record data are globally visible
wait at least the TLSA Record's TTL so old data will expired
deploy the new cert
Is there a suggested way to implement a similar behaviour with the current version (0.6.2) ?
Originally created by @andreasschulze on GitHub (Dec 12, 2018).
When using ACME to issue certificates for Mailservers, one may want to publish TLSA-Records too.
The general timeline would be:
- generate a new private key + req
- issue new cert
- calculate the TLSA-Record data (TLSA Mode 3 3 1)
- put these data into DNS
- make sure, the published TLSA Record data are globally visible
- wait at least the TLSA Record's TTL so old data will expired
- deploy the new cert
Is there a suggested way to implement a similar behaviour with the current version (0.6.2) ?
The following site gives a little useful info on using openssl commands to generate the values for TLSA records (for the public key only) but that alone should give you hints on what to do for the full certs too: https://blog.tyk.nu/blog/generating-tlsa-records-with-openssl/
@jobe1986 commented on GitHub (Dec 12, 2018):
The following site gives a little useful info on using openssl commands to generate the values for TLSA records (for the public key only) but that alone should give you hints on what to do for the full certs too:
https://blog.tyk.nu/blog/generating-tlsa-records-with-openssl/
I also think this doesn't belong directly into dehydrated, but rather into an external hook-script. Thanks for the idea anyway.
@lukas2511 commented on GitHub (Jan 18, 2019):
I also think this doesn't belong directly into dehydrated, but rather into an external hook-script. Thanks for the idea anyway.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @andreasschulze on GitHub (Dec 12, 2018).
When using ACME to issue certificates for Mailservers, one may want to publish TLSA-Records too.
The general timeline would be:
Is there a suggested way to implement a similar behaviour with the current version (0.6.2) ?
@txr13 commented on GitHub (Dec 12, 2018):
Seems this would be better implemented in a hook script’s deploy_cert function.
@jobe1986 commented on GitHub (Dec 12, 2018):
The following site gives a little useful info on using openssl commands to generate the values for TLSA records (for the public key only) but that alone should give you hints on what to do for the full certs too:
https://blog.tyk.nu/blog/generating-tlsa-records-with-openssl/
@esclear commented on GitHub (Dec 16, 2018):
You might want to take a look at DHANE.
@lukas2511 commented on GitHub (Jan 18, 2019):
I also think this doesn't belong directly into dehydrated, but rather into an external hook-script. Thanks for the idea anyway.