unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: 51564@debbugs.gnu.org, 51591@debbugs.gnu.org,
	51555@debbugs.gnu.org, 51559@debbugs.gnu.org,
	Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: bug#51555: bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures.
Date: Thu, 04 Nov 2021 18:23:42 -0400	[thread overview]
Message-ID: <87tugrv9ti.fsf@netris.org> (raw)
In-Reply-To: <YYQAgDBYfqPGUk6K@jasmine.lan>

Hi Leo,

Leo Famulari <leo@famulari.name> writes:

> On Thu, Nov 04, 2021 at 08:57:18AM -0400, Mark H Weaver wrote:
>> Although the WebKitGTK package itself built successfully using GCC 11,
>> the switch to GCC 11 caused many failures in programs that use
>> WebKitGTK.  For example:
>
> Should we just revert the WebKitGTK upgrade for now?

I'm reluctant to do that, because it would mean reintroducing
CVE-2021-30846, CVE-2021-30851 and CVE-2021-42762.  According to
<https://www.webkitgtk.org/security/WSA-2021-0006.html>, two of those
CVEs could allow an attacker to execute arbitrary code via maliciously
crafted web content.

For now, I've reverted back to using clang-11 to compile WebKitGTK,
which works correctly on x86_64-linux, but another fix will be needed to
i686-linux users.  I have some ideas on how to fix it.  I'll write about
that soon at 51591@debbugs.gnu.org.

      Regards,
        Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




      parent reply	other threads:[~2021-11-04 22:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  6:03 bug#51564: Old libsoup package failing system reconfigure Disseminate Dissent via Bug reports for GNU Guix
2021-11-02  6:09 ` bug#51564: Try adding -DUSE_SOUP2 Jacob Hrbek
2021-11-02  6:17 ` bug#51564: (No Subject) Jacob Hrbek
2021-11-02 10:04 ` bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures Liliana Marie Prikler
2021-11-02 13:45   ` Mark H Weaver
2021-11-02 14:10   ` Leo Famulari
2021-11-02 16:08     ` Mark H Weaver
2021-11-02 16:15       ` Liliana Marie Prikler
2021-11-02 17:31         ` Mark H Weaver
2021-11-02 18:10           ` Liliana Marie Prikler
2021-11-03  7:16             ` Mark H Weaver
2021-11-03 17:52               ` Liliana Marie Prikler
2021-11-03 18:09               ` bug#51555: " Mark H Weaver
2021-11-03 19:21                 ` Liliana Marie Prikler
2021-11-03 21:46                   ` Mark H Weaver
2021-11-04  8:29                   ` bug#51559: " Mark H Weaver
2021-11-04 12:57                     ` Mark H Weaver
2021-11-04 15:47                       ` bug#51555: " Leo Famulari
2021-11-04 16:49                         ` bug#51559: " Liliana Marie Prikler
2021-11-04 22:23                         ` Mark H Weaver [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

  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=87tugrv9ti.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=51555@debbugs.gnu.org \
    --cc=51559@debbugs.gnu.org \
    --cc=51564@debbugs.gnu.org \
    --cc=51591@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=liliana.prikler@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).