Re: [9front] acmed bug fixes and external challenge script

[ori@eigenstate.org]

Quoth cinap_lenrek@felloff.net:
> 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
> 

looks great, thanks!