Date: Mon, 3 Apr 2017 10:41:19 +0200 From: Beat Siegenthaler <beat.siegenthaler@beatsnet.com> To: freebsd-questions@freebsd.org Subject: Re: letsencrypt configuration Message-ID: <28d4f822-0f6c-7847-322f-6264e200d196@beatsnet.com> In-Reply-To: <1491201000.3329748.932028040.22FE70EC@webmail.messagingengine.com> References: <77a1e8683e3a15cd08986d66807959b2@drenet.net> <CA%2Bg%2BBvjkSifgxOG9bk6qdu2drt1oY_OhTHdOOsbkKDyJJ0oLgQ@mail.gmail.com> <1491201000.3329748.932028040.22FE70EC@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03.04.17 08:30, Dave Cottlehuber wrote: >> On Sat, Apr 1, 2017 at 2:40 AM, Andre Goree <andre@drenet.net> wrote: >>> So how is everyone going about configuring letsencrypt on FreeBSD? It would >>> seem that multiple ports that used to exist for this very purpose are no >>> longer in the repos (letskencrypt, py-letsencrypt), so tutorials I'm finding >>> (and even letskencrypt, which is still in the FreeBDS wiki) aren't much >>> help. > I speculate that the letsencrypt trademark has been enforced > https://letsencrypt.org/trademarks/ so people needed to rename their > tools. > https://www.freshports.org/security/dehydrated/ Is one of these and my preferred one... dehydrated is a pure BASH implementation of the ACME protocol used by Lets Encrypt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28d4f822-0f6c-7847-322f-6264e200d196>