From: eso@self.rodeo
To: 9front@9front.org
Subject: [9front] [patch] improve http challenge documentation in acmed(8)
Date: Tue, 19 Dec 2023 20:22:04 -0800 [thread overview]
Message-ID: <bb47c92d5d2103c644fa44fb4b868833@self.rodeo> (raw)
working through the example for http challenge in acmed(8) left out a
few steps and clarifications. now, following the example with your
webserver will (should) give your domain https. i also added
/rc/bin/service/!tcp443 as an example service for acmed(8) to reference.
while i was at it, i also updated listen(8) to include tcp80 and tcp443.
eso
diff 66fc6a3e6443d7eb8298f65b0c9803197d196ec7 uncommitted
--- a/sys/man/8/acmed
+++ b/sys/man/8/acmed
@@ -176,11 +176,33 @@
.IR webfs (4)
to be mounted as the ACME protocol uses HTTP
to talk to the provider.
+.PP
+Change -o to be the path your webserver
+will be serving at
+.br
+.BI http:// mydomain.com /.well-known/acme-challenge .
.IP
.EX
-auth/acmed me@example.com /sys/lib/tls/acmed/mydomain.com.csr \\
+auth/acmed -o /path/to/webroot/.well-known/acme-challenge/ \\
+me@example.com /sys/lib/tls/acmed/mydomain.com.csr \\
> /sys/lib/tls/acmed/mydomain.com.crt
.EE
+.PP
+The
+.B cert.key
+must also be loaded into
+.IR factotum (4).
+.IP
+.EX
+cat cert.key > /mnt/factotum/ctl
+.EE
+.PP
+Now you can configure
+.BR /rc/bin/service/tcp443
+to handle
+.br
+HTTPS connections with your webserver of choice.
+.br
.PP
When using the DNS challenge method,
your DNS server
--- a/sys/man/8/listen
+++ b/sys/man/8/listen
@@ -1,6 +1,6 @@
.TH LISTEN 8
.SH NAME
-listen, listen1, tcp7, tcp9, tcp19, tcp21, tcp23, tcp25, tcp53, tcp110,
tcp113, tcp143, tcp445, tcp513, tcp515, tcp564, tcp565, tcp566, tcp567,
tcp993, tcp995, tcp1723, tcp17019, tcp17020 \- listen for calls on a
network device
+listen, listen1, tcp7, tcp9, tcp19, tcp21, tcp23, tcp25, tcp53, tcp80,
tcp110, tcp113, tcp143, tcp443, tcp445, tcp513, tcp515, tcp564, tcp565,
tcp566, tcp567, tcp993, tcp995, tcp1723, tcp17019, tcp17020 \- listen
for calls on a network device
.SH SYNOPSIS
.B aux/listen
.RB [ -iq ]
@@ -182,6 +182,9 @@
.B tcp53
TCP port for DNS.
.TP
+.B tcp80
+HTTP port.
+.TP
.B tcp110
POP3 port.
.TP
@@ -192,6 +195,9 @@
.TP
.B tcp143
IMAP4rev1 port.
+.TP
+.B tcp443
+HTTPS port.
.TP
.B tcp445
CIFS/SMB file sharing.
diff 66fc6a3e6443d7eb8298f65b0c9803197d196ec7 uncommitted
--- /dev/null
+++ b/rc/bin/service/!tcp443
@@ -1,0 +1,4 @@
+#!/bin/rc
+
+# See acmed(8)
+/bin/tlssrv -c/sys/lib/tls/acmed/mydomain.com.crt
/rc/bin/rc-httpd/rc-httpd
next reply other threads:[~2023-12-20 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:22 eso [this message]
2024-01-13 4:27 ` eso
2024-01-13 4:33 ` ori
2024-03-08 5:20 ` ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb47c92d5d2103c644fa44fb4b868833@self.rodeo \
--to=eso@self.rodeo \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).