From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: [9front] acmed bug fixes and external challenge script
Date: Mon, 25 Oct 2021 01:45:03 +0200 [thread overview]
Message-ID: <A6F333ADA1EEB40A1AD6890CBB7119B2@felloff.net> (raw)
ok, got my hands dirty with honest acmed.
dnschallenge was not working for me because apparently
they require a new cca record for the domain in question.
i'v just pushed a fix for ndb/dns so you can specify
one in ndb like:
cca=letsencrypt.org
the tag= and flags= attributes are optional and
default to tag="issue" and flags=0.
next problem is the bullshit with having to pass a domain
manually to achmed when using dns method. this is unneccesary
as the csr already comtains the domains and the protocol
gives you which domain (identifier) a challenge is for.
we just have to use the information (and verify it is
actually listed in the csr as you cant trust the honest
acme server).
and last, my setup is a bit more complicated and just
refreshing /net/dns is not the right thing for me,
so i need a bit of a script that helps with this.
so acmed now allows to use a script command passed
with the -e flag which it runs passing four arguments:
- challenge type
- identifier (domain)
- token
- auth response
with that, i can do the appropriate thing depending
on challenge type and domain.
the rest is just fixing error paths and filedescriptor
leaks.
patch: http://okturing.com/src/12325/body
--
cinap
next reply other threads:[~2021-10-25 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 23:45 cinap_lenrek [this message]
2021-10-25 3:14 ` ori
2021-10-25 18:09 ` sirjofri
2021-10-25 21:49 ` cinap_lenrek
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=A6F333ADA1EEB40A1AD6890CBB7119B2@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).