From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] aclient: a draft.
Date: Sun, 04 Jul 2021 20:37:23 -0700 [thread overview]
Message-ID: <1754E69C7B4969EB009254F9080C9E5B@smtp.pobox.com> (raw)
In-Reply-To: <1250D635-BD43-467A-897F-A3FBA7296989@stanleylieber.com>
Quoth Stanley Lieber <sl@stanleylieber.com>:
> On July 3, 2021 8:52:08 PM EDT, ori@eigenstate.org wrote:
> >I've been working on a client for ACME cert managemnet
> >protocol, RFC8555. It's what letsencrypt uses, as well
> >as several other providers.
> ironically, instead of acme doing everything, we now have everything being called acme.
>
> maybe consider /sys/lib/tls/aclient instead of /sys/lib/tls/acme?*
That is ironic.
Perhaps a foolish thought, but I'll suggest anyway: what if it were
named after the RFC it implements (e.g., /bin/rfc8555/client )?
Boring, but transparent.
next prev parent reply other threads:[~2021-07-07 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 0:52 ori
2021-07-04 15:30 ` Stanley Lieber
2021-07-05 3:37 ` unobe [this message]
2021-07-05 9:01 ` hiro
2021-07-05 23:33 ` ori
2021-07-05 23:34 ` 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=1754E69C7B4969EB009254F9080C9E5B@smtp.pobox.com \
--to=unobe@cpan.org \
--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).