Your message dated Thu, 01 Dec 2016 23:19:46 +0000 with message-id <e1ccadm-000ahv...@fasolo.debian.org> and subject line Bug#837308: fixed in letsencrypt.sh 0.3.0-1 has caused the Debian Bug report #837308, regarding letsencrypt.sh: version 0.3.0 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 ow...@bugs.debian.org immediately.) -- 837308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---source: letsencrypt.sh version: 0.2.0-4 severity: wishlist Upstream added in v0.3.0 multi-account support. Though in doing so it dropped support for ACCOUNT_KEY and ACCOUNT_KEY_JSON variables, in favour of some mess. See upstream commit 034ec30c7d3f098007ffee704b00cf2d3c9b78e9 https://anonscm.debian.org/git/letsencrypt/letsencrypt.sh.git/commit/?h=upstream/master&id=034ec30c7d3f098007ffee704b00cf2d3c9b78e9 I've yet to try it myself, but as I see it if users wants to keep their account keys that are not set to the place where upstream would dream of (${BASE_DIR}/private_key.pem), they need to move them themselves to the final place. Also doesn't help that: * the path is kinda unobvious: (in bash format) ${ACCOUNTDIR:${BASEDIR}/accounts}/$(echo ${CA} | urlbase64}/ really, hashing $CA ?? Why I wonder… Besides, `urlbase64` doesn't seem to be a thing in Debian (‽) * the filenames changed too: private_key.pem => account_key.pem private_key.json => registration_info.json and they are not configurable anymore I know that the DSA (Debian System Administrators) use the ACCOUNT_KEY setting for their letsencrypt.sh deployment¹, and where annoyed because their usage was not covered in our upgrade path in the last "migration". So, I'd love to see even a more nifty thing this time :) ¹ https://anonscm.debian.org/git/mirror/letsencrypt-domains.git/tree/config/letsencrypt-config though atm it still uses the old PRIVATE_KEY there. I asked why, considering that at update time I received rants over IRC for that… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: letsencrypt.sh Source-Version: 0.3.0-1 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 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo <mat...@debian.org> (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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 02 Dec 2016 00:04:30 +0100 Source: letsencrypt.sh Binary: letsencrypt.sh letsencrypt.sh-apache2 Architecture: source Version: 0.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Let's Encrypt <letsencrypt-de...@lists.alioth.debian.org> Changed-By: Mattia Rizzolo <mat...@debian.org> Description: letsencrypt.sh - ACME client implemented in Bash letsencrypt.sh-apache2 - letsencrypt.sh challenge response support for Apache2 Closes: 837308 838942 839851 846319 Changes: letsencrypt.sh (0.3.0-1) unstable; urgency=medium . * Import new upstream release 0.3.0. + Remove all Debian patches (as they were coming from upstream). + Add patch to revert the upstream commit renaming config.sh to config. Let's avoid another breaking change at this point, keep it for the dehydrated upload. + Add NEWS entry about the ACCOUNT_KEY move. + Closes: #839851 * Bump debhelper compat level to 10. * Add dependency on ca-certificates. Closes: #838942 * Add patch from upstream to fix support of OpenSSL 1.1.0. Closes: #846319 * Add patch to account for an already set ACCOUNT_KEY option when upgrading to the multi-account structure. Closes: #837308 Checksums-Sha1: 1dc89614b35da550bc35abefa9cd571c5c181129 2113 letsencrypt.sh_0.3.0-1.dsc 127c7373a9cf45adb84aba8a8deda5b1f9b17daa 21304 letsencrypt.sh_0.3.0.orig.tar.gz 2db50fdfe713ad85580ac6e3846dda9d2c5edcc2 11232 letsencrypt.sh_0.3.0-1.debian.tar.xz Checksums-Sha256: a877477fa7fa5e3ebc64a48f9216b0d8f2c8daeaccbe0488a02fdf38e743bf4a 2113 letsencrypt.sh_0.3.0-1.dsc 2e99ea4ba29d9179f704da48c710d1025cd5a8a4cfcf0fdb2215d9cb3a1f95a5 21304 letsencrypt.sh_0.3.0.orig.tar.gz 965ec96944ee440caf45483da58ae7a9aae9a79be69ce662beb9b8146cefb4f8 11232 letsencrypt.sh_0.3.0-1.debian.tar.xz Files: a097dc1ca5a49732859d1e9bb5bf91b2 2113 misc optional letsencrypt.sh_0.3.0-1.dsc 0e84e2b128b9fdd925dbbec33e7075ad 21304 misc optional letsencrypt.sh_0.3.0.orig.tar.gz 0c58c97d5573049ebddcc7f30278dd80 11232 misc optional letsencrypt.sh_0.3.0-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJYQK0JAAoJEAgWueGMdiutkK4P/itJ1nZStx917O7Phwu17eAQ 7GOqfHBB08lttAwB0VoOOXYYa9P3+gxhT+EPSzSEcwZ+8WRFxWXVvOxt3ku52CX4 f7EJ9QmZbYLWld+3FaVCAdxY6WziKYwti1mlZ+mMuLcNMxqF1YmwZwqpWs4pd5E+ GuJ4LFo+B1MlKz8MiB7fAxGhg8Ukydh80rMfH2LUXZOuRCjUAb/+6yq/LRDMhLTk U+JqPmiD93MMgWV2vTol23tHS9JQtvVdb2GVQKm6YGrEYV3nAF+Wb8XqWq4dFR79 pA8b7kQxg54Wyxjy63+yi4vfReHpAUqWbTu7EsdnTgVNsvhpCr1QxS2ZnyIImJ4A ok5g3AGtcqKJ9hb7p0UjaiWac65AJ4WWLy+1a+yvKk3UCh5V2CzOx9uWtOjaq6VP 9Oy7m99K8lmS++AQ1q4fkwjUtX/2rDJy4/BVsC/DioXTnfUUSLnvC8DUaSq16wrI unFdi35y/5G0U6DFlhEeFMR4HUTXcYzxHTVvi4t1w7oreUUlc7peFMfhtrCD05+i HJeZO6EENpsWWsxGB55LnFhebd/k1aLlbICna7BBTdXGptwhEY8nS+TNmwg6XSDb eGipex0+CDeV3YrZ3OgmQf126LEgX+u/Bmmk+5eRJ9BppCKQCPXfg/aJTiuVMlym 79qGh5rF1QNrTLLiV63k =hYF+ -----END PGP SIGNATURE-----
--- End Message ---
