47 | This is an 48 | ACME 55 | server, similar to what 56 | LetsEncrypt 63 | runs. 64 |
65 |66 | But, instead of signing your certificates being signed by a 67 | trusted CA, it creates a self-signed certificate. This can be used 68 | with 69 | DANE 76 | to secure Handshake websites. 77 |
78 |91 | # Install certbot (or any client) normally: 92 | https://certbot.eff.org/
99 | # Get a certificate and install it like:
100 | sudo certbot --nginx -d your_tld.or_sld \
101 | --server https://acme.htools.work/directory 102 | --reuse-key 103 |
104 | # Finally, set the TLSA record from 105 | https://acme.htools.work/tlsa 112 |
Why does this even exist?
117 |118 | Because you can use any ACME client (like 119 | certbot) and take advantage of existing plugins for all kinds of web 126 | servers. Also, there's no need to bother with OpenSSL and TLSA. 127 |
128 |What if the CA is compromised?
131 |132 | Nothing happens. A new CA key is generated for every issued 133 | certificate and then destroyed immediately. And with DANE, it 134 | really wouldn't matter anyway. 135 |
136 |I want the TLSA email.
139 |140 | To receive emails containing TLSA records when certificates are 141 | issued, add a 142 | +email 146 | to the end of your email address like: 147 | foobar+email@gmail.com. 151 |
152 |