Russ Allbery writes:
> Paul Wise writes:
>> I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
>> available in Ubuntu xenial, which is scheduled for 5 years of support,
>> terminating in 2021.
> It's in universe, so it's not really included in that five-year promise.
We're also in
Paul Wise writes:
> On Tue, Nov 22, 2016 at 9:40 AM, Peter Eckersley wrote:
>> currently working with an ACME backwards compatibilty window of 6-12
>> months, but probably not longer than that.
> I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
> available in Ubuntu xenial, whic
On Tue, Nov 22, 2016 at 9:40 AM, Peter Eckersley wrote:
> currently working with an ACME backwards compatibilty window of 6-12 months,
> but probably not longer than that.
I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
available in Ubuntu xenial, which is scheduled for 5 years
On 11/22/2016 02:40 AM, Peter Eckersley wrote:
> 1. Leave Certbot out of the Debian Stretch release, and rely on
> backports as the recommended way to run Certbot on Debian. That's what we
> currently do with Jessie:
Note that per backports rules, $RELEASE_N-backports must track
$RELEASE_N_PLUS_1,
> "PE" == Peter Eckersley writes:
PE> 1. Leave Certbot out of the Debian Stretch release, and rely on
PE> backports as the recommended way to run Certbot on Debian. That's what we
PE> currently do with Jessie:
PE> https://certbot.eff.org/#debianjessie-apache
The jessie and jessie-backports
On 23/11/16 09:57, Thijs Kinkhorst wrote:
> Hi Peter,
>
> On Tue, November 22, 2016 02:40, Peter Eckersley wrote:
>> I'm an upstream developer for Certbot, previously known as the Let's
>> Encrypt client (https://certbot.eff.org). Certbot is a flexible and very
> popular
>> way to get certificat
Hi Peter,
On Tue, November 22, 2016 02:40, Peter Eckersley wrote:
> I'm an upstream developer for Certbot, previously known as the Let's
> Encrypt client (https://certbot.eff.org). Certbot is a flexible and very
popular
> way to get certificates from Let's Encrypt;
Thanks a lot for your efforts.
On Mon, Nov 21, 2016 at 05:40:22PM -0800, Peter Eckersley wrote:
> The ACME protocol that it uses to talk to Let's
> Encrypt is also rapidly evolving through an IETF working group
> (https://datatracker.ietf.org/wg/acme/charter/), and the Let's Encrypt
> server-side codebase (https://github.com/let
8 matches
Mail list logo
