On Sat, Nov 18, 2017 at 04:25:38PM +0100, Jan Wagner wrote:
> > I'll see about getting
> > https://anonscm.debian.org/git/letsencrypt/dehydrated.git/commit/?h=debian/stretch&id=5ae0ba0674a4913bcd27e16d02bacf486e570c83
> > in the next point release.
> 
> I think this is NOT the best idea, cause this will just only help until
> the next LICENSE is published and this has to be fixed again.

That's right.
But I fear for stretch (and jessie-backports) we will have to live with
having to update the agreements URL whenever LE decides to update them
(till now it seemed to be ~yearly, so it's not really a problem).

> > AFAIK 0.4.0 is not affected because it downloads the last agreements at
> > registration time, and therefore doesn't hardcode this URL.
> 
> No, it's fixed there.

How is this different from what I wrote?

> The issue for this is
> https://github.com/lukas2511/dehydrated/issues/346 and it was fixed in
> https://github.com/lukas2511/dehydrated/commit/6a32f20e004b9d835cd02de9d78300be02784cf1.

Yes, but it's something too big for my testes, and it also includes a
behavioural change which is not acceptable for a stable update.

stretch-backports contains 0.4.0 which of course contains the commit you
linked.

-- 
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  `-

Attachment: signature.asc
Description: PGP signature

Reply via email to