From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update)
Date: Wed, 10 Feb 2016 15:46:03 -0500 [thread overview]
Message-ID: <87io1wnvjo.fsf@netris.org> (raw)
In-Reply-To: <20160210144659.GA7093@debian.eduroam.u-bordeaux.fr> (Andreas Enge's message of "Wed, 10 Feb 2016 15:46:59 +0100")
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> On Tue, Feb 09, 2016 at 03:15:38PM -0500, Mark H Weaver wrote:
>> Alas, this will require at least 7000 rebuilds. After the current
>> 'security-updates' branch is merged, this should go on the next
>> 'security-updates' branch, together with more fixes for graphite2 and
>> libsndfile.
>
> it looks like we are almost there. Do you think we could squeeze in an
> evaluation and build of wip-pulseaudio after updating master and rebasing
> the wip branch on master?
I'm reluctant to delay a critical security update like this, which
apparently allows a compromised web site to perform remote code
execution in our graphical web browsers. I, for one, am running
text-only for now, and am impatient to return back to the modern era.
What's the nature of the pulseaudio update? Why is it important?
What do other people think?
Mark
next prev parent reply other threads:[~2016-02-10 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 19:52 [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update) Christopher Allan Webber
2016-02-09 20:15 ` Mark H Weaver
2016-02-09 20:31 ` Christopher Allan Webber
2016-02-10 14:46 ` Andreas Enge
2016-02-10 16:53 ` wip-pulseaudio (was Re: [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update)) Efraim Flashner
2016-02-10 18:41 ` Efraim Flashner
2016-02-10 18:55 ` Andreas Enge
2016-02-10 20:43 ` Andreas Enge
2016-02-10 20:46 ` Mark H Weaver [this message]
2016-02-10 20:56 ` [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update) Andreas Enge
2016-02-11 9:52 ` Ludovic Courtès
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=87io1wnvjo.fsf@netris.org \
--to=mhw@netris.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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).