From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 46183-done@debbugs.gnu.org, Ryan Prior <rprior@protonmail.com>
Subject: bug#46183: [PATCH 0/1] Update gcrypt [URGENT SECURITY ISSUE]
Date: Mon, 01 Feb 2021 12:50:49 +0100 [thread overview]
Message-ID: <87k0rsgg6e.fsf_-_@gnu.org> (raw)
In-Reply-To: <878s8astsb.fsf@yamatai> (Guillaume Le Vaillant's message of "Sat, 30 Jan 2021 09:39:16 +0100")
Hi,
Guillaume Le Vaillant <glv@posteo.net> skribis:
> According to the news at https://gnupg.org:
>
> Libgcrypt 1.9.1 released (2021-01-29) important
>
> Unfortunately we introduced a severe bug in Libgcrypt 1.9.0 released 10 days ago.
> If you already started to use version 1.9.0 please update immediately to 1.9.1.
>
> Currently the master and staging branch are using libgcrypt 1.8.5 and
> core-updates is using 1.8.7. These versions don't have the critical bug
> as it was introduced in version 1.9.0. So I think updating libgcrypt on
> master is not an emergency, we just have to remember to never use
> version 1.9.0.
Indeed. So closing this bug. That said, we can update libgcrypt in
‘core-updates’.
Ludo’.
next prev parent reply other threads:[~2021-02-01 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 4:20 [bug#46183] [PATCH 0/1] Update gcrypt [URGENT SECURITY ISSUE] guix-patches--- via
2021-01-30 4:24 ` [bug#46183] [PATCH 1/1] gnu: libgcrypt: Update to 1.9.1 guix-patches--- via
2021-01-30 8:08 ` guix-patches--- via
2021-01-30 8:39 ` Guillaume Le Vaillant
2021-02-01 11:50 ` Ludovic Courtès [this message]
2021-01-30 7:56 ` [bug#46183] [PATCH 0/1] Update gcrypt [URGENT SECURITY ISSUE] lordyuuma
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0rsgg6e.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=46183-done@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=rprior@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).