From: Kyohei Kadota <lufia@lufia.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] lets encrypt
Date: Fri, 18 Oct 2019 00:00:57 +0900 [thread overview]
Message-ID: <CAFMepcm8N22K_H1bfBwxrcrtHq-Cs_ecSNU71SNdEFU4+u3kfA@mail.gmail.com> (raw)
In-Reply-To: <7F4B972A-9548-40CF-B760-0CC45F59BB33@corpus-callosum.com>
I use go-acme/lego too.
Lego uses ec384 by default, so I specify -k rsa2048 option.
2019年10月17日(木) 23:41 Jeff Sickel <jas@corpus-callosum.com>:
>
> I’ve been testing lego (https://go-acme.github.io/lego/) to test wildcard
> certificates. It works well, though there are some manual bits required
> every 60 days to keep certain services using the certificates.
>
> -jas
>
> > On Oct 17, 2019, at 4:56 AM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> >
> > I use Go's crypto/acme package. It works with the http package seamlessly.
> > https://godoc.org/golang.org/x/crypto/acme
> >
> >
> > On Thu, Oct 17, 2019, 2:12 AM Steve Simon <steve@quintile.net> wrote:
> > 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
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T12cdd20280545377-M760dcb2f6181fab98e39b601
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2019-10-17 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:11 Steve Simon
2019-10-17 9:56 ` [9fans] " Skip Tavakkolian
2019-10-17 14:40 ` Jeff Sickel
2019-10-17 15:00 ` Kyohei Kadota [this message]
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=CAFMepcm8N22K_H1bfBwxrcrtHq-Cs_ecSNU71SNdEFU4+u3kfA@mail.gmail.com \
--to=lufia@lufia.org \
--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).