Your message dated Sat, 21 May 2016 13:51:16 +0000
with message-id <[email protected]>
and subject line Bug#824903: fixed in letsencrypt.sh 0.1.0-3
has caused the Debian Bug report #824903,
regarding letsencrypt.sh: Letsencrypt.sh broken due to "pretty" json used in
Let's Encrypt API
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
824903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824903
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: letsencrypt.sh
Version: 0.1.0-2~bpo8+1
Severity: normal
File: /usr/bin/letsencrypt.sh
Hi,
I'm testing this using the backports package, but I guess the problem
applies to sid as well (same version).
Recently letsencrypt.org changed to return pretty json with lots of
newlines (as tested via
https://acme-staging.api.letsencrypt.org/directory). This breaks
various sed-based json parsing code in the distributed version of
letsencrypt.sh .
The symptom is that 'letsencrypt.sh --cron' silently exits after
printing
+ Requesting challenge for <servername>
Aborting before completing the challenge.
Looking at trace output from
bash -x -c 'source /usr/bin/letsencrypt.sh --cron'
It obviously fails to extract the challenge from json output due to
sed -n 's/.*\("challenges":[^\[]*\[[^]]*]\).*/\1/p'
expecting the hole match to be on a single line. Somebody reported the
issue upstream on May 18th:
https://github.com/lukas2511/letsencrypt.sh/pull/202
The "official" fix is here:
https://github.com/lukas2511/letsencrypt.sh/commit/561f0626b855ec4ee94856884e2f1eff9ade2d88
cheers,
David
- -- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages letsencrypt.sh depends on:
ii curl 7.38.0-4+deb8u3
ii openssl 1.0.1k-3+deb8u5
letsencrypt.sh recommends no packages.
letsencrypt.sh suggests no packages.
- -- no debconf information
- --
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7 7F1D 935E 6F08 E457 205F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iF4EAREIAAYFAlc/5WIACgkQk15vCORXIF+G/gD/YYZYGZDLM6Jb64JCtWojJCqP
dLaNFWQkMUqrfuizXJkBAKmJjaUMs8PHREkge9T1oIjVzukCQA7dz9Y2OndEAxIx
=nAa2
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: letsencrypt.sh
Source-Version: 0.1.0-3
We believe that the bug you reported is fixed in the latest version of
letsencrypt.sh, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mattia Rizzolo <[email protected]> (supplier of updated letsencrypt.sh package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 21 May 2016 13:37:22 +0000
Source: letsencrypt.sh
Binary: letsencrypt.sh letsencrypt.sh-apache2
Architecture: source
Version: 0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt <[email protected]>
Changed-By: Mattia Rizzolo <[email protected]>
Description:
letsencrypt.sh - ACME client implemented in Bash
letsencrypt.sh-apache2 - letsencrypt.sh challenge response support for Apache2
Closes: 822493 824903
Changes:
letsencrypt.sh (0.1.0-3) unstable; urgency=medium
.
[ Daniel Beyer ]
* Add a README.Debian for binary package letsencrypt.sh. Closes: #822493
.
[ Mattia Rizzolo ]
* Import patch from upstream to work with the new "pretty" json used in the
Let's Encrypt API. Closes: #824903
Checksums-Sha1:
e19deed0b9d1561e254f1a1a049efa715c12242f 2109 letsencrypt.sh_0.1.0-3.dsc
123d7ae9258d9ef4b1b6fd0e34eaa159e72ceb25 6252
letsencrypt.sh_0.1.0-3.debian.tar.xz
Checksums-Sha256:
5793048c56308f173d84fdc6b123c8f7f96c91146938e50bd3d5bb3539c1233f 2109
letsencrypt.sh_0.1.0-3.dsc
3a03ecb6726aced6b6170299a85a20e223714f29b94801c2251ecad8a4d86ad9 6252
letsencrypt.sh_0.1.0-3.debian.tar.xz
Files:
c705b1317e409a6a52d306778d0ec6a7 2109 misc optional letsencrypt.sh_0.1.0-3.dsc
df0b2505412cab0f03808c2ad15dc8c1 6252 misc optional
letsencrypt.sh_0.1.0-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJXQGTsAAoJEEsEP825REVA+F0P/2yy5ohmlWaqgxxz0alvoYYa
5FmK0lpL0mxbn9ylyyR4qOZS/RxT1jSrvxzbQAu7vYvrtD4cF1sgWldEfbp72u2Z
HpbHjL5Fzy7fuf28+82RDHlHmWgBwh/yj5fMGzhz5G4y3x2sZtQHcU9Wke3IhhiY
+FkfdemPLkAWZVsFCj4CY4TgIyQxdkB1KMLmFfw/+9lHtavwcUU7lSsDyg0Gwdy8
jJwyDhMl2/m+C3wOc8H5mN3kb6Onyac42PqbEbap/dKfz+IMFjwOK6W4m/tTPZV+
kGDFwGhgFeJL3iGNa+XRyoZ+jwBUQZbDmYdS/d19cxyIH+rBgnx4xKHBFz4Za6x2
0xBx8bO1EGIhB10//MkyIMDiSwCLrPVuU2iWX9fSQEFplOZMrzZUslAem6TMsAO0
Qywm/C7xF9mGjaFdVmaDnl9lzPx/UWVqw4srb2P6ycRRLCOhA5LC3rqUveAmkcYt
mmUtomwyclB9kVIJzAfzRDXfoQjjNXBI0wwUvTvsv1RaqCBypAf+L2RsyzEikg88
IGZuhvpjCuPxCkOoo+S3yg278Z8TganoQNcQMdQGITNPeEgb153yfq4OFO6xNVJK
WhWXBP3GjKtNsMrmpUYkXFqVio5bjgKDTDvsbV6AXhBBfBIg6CTgBfsqb5TozqZc
vTTNC+CoGFWO9iuXEs1k
=vEWi
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Letsencrypt-devel mailing list
[email protected]
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
