commit 23fbeaf8316052feaef8941e0e611bc16948e019 (patch)
parent d249498fd2051c2cf380cd91970f8acc4b4d18bc
Author: alex <alex@garbash.com>
Date: Mon, 2 May 2022 23:33:10 -0400
notes: Correct the name of the IRC client in 013-wildcard
It's gamja, not soju!
Diffstat:
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/notes/013-wildcard-cert.md b/notes/013-wildcard-cert.md
@@ -9,7 +9,8 @@ Thur Apr 28, 2022
I've been running two internal services for a while:
* lists.garbash.com -- mailing list archive
-* irc.garbash.com -- [soju](https://soju.im) IRC client
+* irc.garbash.com -- [gamja](https://git.sr.ht/~emersion/gamja) IRC client
+ (and [soju](https://soju.im) bouncer)
Because we're not using split DNS (hosting our own DNS server for
clients on the VPN), these are kept internal only by having the public
@@ -27,7 +28,7 @@ certs need to be publicly accessible for HTTP challenges.
It would have been OK to serve over plain HTTP (in the sense that the
services are served over a wireguard tunnel, so they're already encrypted),
but browsers only allow desktop notifications for HTTPS sites, so to get
-notifications for `soju`, I needed a wildcard cert.
+notifications for `gamja`, I needed a wildcard cert.
The wildcard cert turned out to be not too hard. For a couple months I
used [`uacme`](https://github.com/ndilieto/uacme) because it was in ports,
