From: Steve Simon <steve@quintile.net>
To: 9fans@9fans.net
Subject: lets encrypt
Date: Thu, 17 Oct 2019 10:11:53 +0100 [thread overview]
Message-ID: <FFF0F554-DA9F-4724-997D-4B206058AB21@quintile.net> (raw)
hi
anyone using let's encrypt to generate signed certificates for tls, and is using a scripted interface on plan9 to refresh them every 60 days?
care to share the details.
-Steve
next reply other threads:[~2019-10-17 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:11 Steve Simon [this message]
2019-10-17 9:56 ` [9fans] " Skip Tavakkolian
2019-10-17 14:40 ` Jeff Sickel
2019-10-17 15:00 ` Kyohei Kadota
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=FFF0F554-DA9F-4724-997D-4B206058AB21@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).