link to ansible

[web.git] / personal / _posts / 2017-12-26-lets-encrypt.md

diff --git a/personal/_posts/2017-12-26-lets-encrypt.md b/personal/_posts/2017-12-26-lets-encrypt.md
index f8f848d315eba3836af274ae2f8d51eea85f5cbd..3f4fbee3edd74453ed96b1dcacc87be74e1b7086 100644 (file)
--- a/personal/_posts/2017-12-26-lets-encrypt.md
+++ b/personal/_posts/2017-12-26-lets-encrypt.md
@@ -26,11 +26,12 @@ The client is based on [acme-tiny](https://github.com/diafygi/acme-tiny), a
 beautifully small Python library (<200 lines) speaking the ACME protocol.
 That's the protocol developed by Let's Encrypt to communicate with an automated
 CA.  I duly called my client "Let's Encrypt Tiny", and with less than 250 lines
-I think that name is still fair.  For now,
-[Let's Encrypt Tiny](https://github.com/RalfJung/server-scripts/blob/master/letsencrypt-tiny)
-resides in my [server-scripts](https://github.com/RalfJung/server-scripts)
-repository, and it will stay there until anyone else has an interesting in using
-it. ;)
+I think that name is still fair.  For now, Let's Encrypt Tiny resides in my
+[server-scripts](https://github.com/RalfJung/server-scripts) repository, and it
+will stay there until anyone else has an interesting in using it. ;)
+
+**Update:** Let's Encrypt Tiny now has its
+[own repository](https://github.com/RalfJung/lets-encrypt-tiny). **/Update**
 
 The central concept of Let's Encrypt Tiny is a "certificate line" -- a sequence
 of certificates, possibly for different private keys, that "belong together" in
@@ -258,4 +259,4 @@ added to my zone.  At least 25h later (I have the TTL set to 24h), the key gets
 unstaged, and the old TLSA record is removed from the zone.
 
 That's it!  If you have any questions, feel free to report
-[issues at GitHub](https://github.com/RalfJung/server-scripts/issues).
+[issues at GitHub](https://github.com/RalfJung/lets-encrypt-tiny/issues).