All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/x11r7/xserver_xorg-server: add security fix for CVE-2020-14347
Date: Fri, 28 Aug 2020 19:03:20 +0200	[thread overview]
Message-ID: <ovpn1hxmln.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20200811234906.051e8caa@windsurf.home

Am Tue, 11 Aug 2020 23:49:06 +0200 schrieb Thomas Petazzoni via buildroot:

> This raises a question: what about the older X.org server releases?
> According to the NIST CVE entry, all versions prior to 1.20.9 are
> affected, so should the patch be backported to the other X.org server
> versions we support ?

Hi Thomas,

the bump to 1.20.9 fixed four CVEs in total which makes backporting 
upstream patches more complicated as time passes by and new issues arise, 
upstream does not update the older branches anymore:
https://cgit.freedesktop.org/xorg/xserver/

Due to the fact that personally I have no use for the older X.org server 
versions I would like to raise the question whether we can remove them? 
From my POV these older versions are unmaintained in buildroot because I 
want to concentrate on the current release which is the one I am using.

Regards, Bernd

  reply	other threads:[~2020-08-28 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  6:41 [Buildroot] [PATCH 1/1] package/x11r7/xserver_xorg-server: add security fix for CVE-2020-14347 Bernd Kuhls
2020-08-11 21:49 ` Thomas Petazzoni
2020-08-28 17:03   ` Bernd Kuhls [this message]
2020-08-28 18:48     ` Peter Korsgaard
2020-08-29 11:36       ` Bernd Kuhls
2020-08-28 15:54 ` Peter Korsgaard
     [not found] ` <fbd81a16-35f0-5e1a-73fb-1b9c703a9408@t-online.de>
2020-08-28 18:56   ` [Buildroot] [PATCH 1/1] package/x11r7/xserver_xorg-server: add security fix Thomas Petazzoni

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=ovpn1hxmln.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.