unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 48039@debbugs.gnu.org
Subject: [bug#48039] xorg-server might be vulnerable to CVE-2021-3472
Date: Mon, 26 Apr 2021 15:33:33 -0400	[thread overview]
Message-ID: <YIcVjQ/oLozIA8Ki@jasmine.lan> (raw)
In-Reply-To: <8735vcsxxt.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>

On Mon, Apr 26, 2021 at 08:27:58PM +0200, Nicolò Balzarotti wrote:
> Leo Famulari <leo@famulari.name> writes:
> 
> > On Mon, Apr 26, 2021 at 07:25:35PM +0200, Nicolò Balzarotti wrote:
> >> * gnu/packages/xorg.scm (xorg-server): Update to 1.20.11.
> >
> > Did you see <https://bugs.gnu.org/48001>?
> >
> Ops, sorry for the duplicate, I somehow missed it, I'm closing this

I didn't mean for you to close your message.

We took different approaches to fixing the bug: I applied a patch, and
you updated the package.

The big difference is that your patch doesn't avoid changing the
xorg-server-for-tests package, so it can't be applied to master.

I'm merging the two tickets. I think that updating the package is a
better choice that simply patching it. I'll probably join our two
patches together and push that.




       reply	other threads:[~2021-04-26 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878s55rm9c.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
     [not found] ` <YIb53KSJPfQf5mn6@jasmine.lan>
     [not found]   ` <8735vcsxxt.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
2021-04-26 19:33     ` Leo Famulari [this message]
2021-04-27  6:02       ` bug#48039: xorg-server might be vulnerable to CVE-2021-3472 Leo Famulari
2021-04-27  7:18         ` [bug#48039] " Nicolò Balzarotti

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=YIcVjQ/oLozIA8Ki@jasmine.lan \
    --to=leo@famulari.name \
    --cc=48039@debbugs.gnu.org \
    --cc=anothersms@gmail.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).