Re: [Letsencrypt-devel] Certbot in Debian Stretch

2016-11-30 Thread Peter Eckersley
On Wed, Nov 30, 2016 at 10:34:11PM +0100, Christian Seiler wrote: > Ah, and I ran my strace earlier with -e open,access, but after > rechecking it, it does in fact check for the file's existence > via stat(). I should remember to use -e open,access,stat when > checking for file access with

Re: [Letsencrypt-devel] Certbot in Debian Stretch

2016-11-30 Thread Peter Eckersley
On Tue, Nov 29, 2016 at 09:59:06AM +0100, Daniel Pocock wrote: > This would probably mean making sure the client is checking the network > API version and giving the user helpful, distro-specific instructions if > there is a mismatch, e.g. a Debian user would see a message "The Let's > Encrypt

[Letsencrypt-devel] Bug#839851: Bug#839851: [letsencrypt.sh] New upstream available

2016-11-30 Thread Mattia Rizzolo
On Wed, Oct 05, 2016 at 08:13:53PM +0200, Jan Wagner wrote: > thanks for working hard on the letsencrypt.sh packages and doing such a > great job. It would be a lot easier and more stimulating if upstream cared more about backward compatibility. Every single update has some breakage, which we

[Letsencrypt-devel] Bug#846319: letsencrypt.sh: Fails to create fullchain.pem

2016-11-30 Thread Chris Boot
Package: letsencrypt.sh Version: 0.2.0-4 Severity: grave Tags: upstream patch Justification: renders package unusable Dear maintainer, Since openssl 1.1 has migrated to stretch I am unable to renew my Let's Encrypt certificates using letsencrypt.sh. The symptoms are: + Challenge is valid! +