Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wayland: bump to version 1.21.0
Date: Thu, 15 Dec 2022 16:29:50 +0100	[thread overview]
Message-ID: <87zgbor8gh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <450d76a0-6324-5ec5-e3ba-e9f615555810@theobroma-systems.com> (Quentin Schulz's message of "Thu, 15 Dec 2022 14:20:40 +0100")

>>>>> "Quentin" == Quentin Schulz <quentin.schulz@theobroma-systems.com> writes:

Hi,

 > It cleanly applies after
 > https://gitlab.freedesktop.org/wayland/wayland/-/commit/03e8a1f84b6a15c9531db1ca8d0a25f9fcffaf25 
 > is applied too. So that could be an option too yes.

OK, good. Then I would prefer that for 2022.02.x.


 > There doesn't seem to be an exploit PoC available somewhere (as is
 > often the case) and I wouldn't even have a machine at hand with that
 > much RAM/swap to test this properly if there was one.

It indeed doesn't sound like a very relatistic vulnerability for a
Buildroot system. I guess you flagged it just because it comes up by the
CVE scan rather than any real concerns about the vulnerability?


 > As for the reverse dependencies, I was planning on doing a simple test
 > with weston (which is the only compositor we use) but that is of the 
 > same version in 2022.02.x that it is in master so that won't tell us much.

 > Are you concerned about something specifically? Is there something
 > you'd want me to check?

No, nothing specific - We just don't have any runtime tests for wayland,
so it is handy if you have a working setup where you can do a quick
smoke test.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-12-15 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 21:53 [Buildroot] [PATCH 1/1] package/wayland: bump to version 1.21.0 James Hilliard
2022-09-21 20:09 ` Thomas Petazzoni
2022-12-12 14:32 ` Quentin Schulz via buildroot
2022-12-14 19:15   ` Peter Korsgaard
2022-12-15 13:20     ` Quentin Schulz via buildroot
2022-12-15 15:29       ` 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=87zgbor8gh.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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