From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/uacme: bump version to 1.2.3
Date: Mon, 27 Jul 2020 22:07:00 +0200 [thread overview]
Message-ID: <87h7tsu3h7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200508163951.5hf2clb4cysufywb@einstein.dilieto.eu> (Nicola Di Lieto's message of "Fri, 8 May 2020 18:39:51 +0200")
>>>>> "Nicola" == Nicola Di Lieto <nicola.dilieto@gmail.com> writes:
> On Fri, May 08, 2020 at 10:11:00AM +0200, Peter Korsgaard wrote:
>> Does that also affect the 1.0.21 version we have in 2020.02.x? If so,
>> what is the impact? Do we need to update to 1.2.3 or cherry pick a
>> patch?
>>
> Yes, all versions prior to 1.2.3 are affected. The impact for the
> moment is only with pebble (the non-production standalone let's
> encrypt testing server, https://github.com/letsencrypt/pebble).
> The production let's encrypt server runs a different software
> (boulder) which doesn't trigger this bug, however this may change and
> I have no control over whether or when this will happen.
> Therefore I recommend updating to a newer version. Also note that I
> released 1.3 about one hour ago which has a few more small fixes and
> enhancements, see https://github.com/ndilieto/uacme/blob/master/NEWS
Sorry for the slow reponse, I have now updated 2020.02.x to 1.2.4.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-07-27 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 5:51 [Buildroot] [PATCH] package/uacme: bump version to 1.2.3 Nicola Di Lieto
2020-04-23 20:50 ` Thomas Petazzoni
2020-05-08 8:11 ` Peter Korsgaard
2020-05-08 16:39 ` Nicola Di Lieto
2020-05-09 7:09 ` Peter Korsgaard
2020-05-09 7:39 ` Nicola Di Lieto
2020-07-27 20:07 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7tsu3h7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox