public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: enable build flag -fstack-protector-strong for improved security
Date: Fri, 07 Aug 2026 16:05:46 GMT	[thread overview]
Message-ID: <178611874638.1.2803746009515768765.rpms-chromium-88b401e09e62@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 88b401e09e621069353d95a06ad361f57832765f
Author : Than Ngo <than@redhat.com>
Date   : 2023-12-02T21:48:27+01:00
Stats  : +19/-1 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/88b401e09e621069353d95a06ad361f57832765f?branch=epel9-next

Log:
enable build flag -fstack-protector-strong for improved security

---
diff --git a/chromium-119-fstack-protector-strong.patch b/chromium-119-fstack-protector-strong.patch
new file mode 100644
index 0000000..688938d
--- /dev/null
+++ b/chromium-119-fstack-protector-strong.patch
@@ -0,0 +1,12 @@
+diff -up chromium-119.0.6045.199/build/config/compiler/BUILD.gn.me chromium-119.0.6045.199/build/config/compiler/BUILD.gn
+--- chromium-119.0.6045.199/build/config/compiler/BUILD.gn.me	2023-12-02 12:19:01.138079722 +0100
++++ chromium-119.0.6045.199/build/config/compiler/BUILD.gn	2023-12-02 12:21:05.835322037 +0100
+@@ -379,7 +379,7 @@ config("compiler") {
+           cflags += [ "-fno-stack-protector" ]
+         } else if (current_os != "aix") {
+           # Not available on aix.
+-          cflags += [ "-fstack-protector" ]
++          cflags += [ "-fstack-protector-strong" ]
+         }
+       }
+     }

diff --git a/chromium.spec b/chromium.spec
index 170ba47..5e2eee6 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -267,7 +267,7 @@
 
 Name:	chromium%{chromium_channel}
 Version: 119.0.6045.199
-Release: 1%{?dist}
+Release: 2%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
 License: BSD-3-Clause AND LGPL-2.1-or-later AND Apache-2.0 AND IJG AND MIT AND GPL-2.0-or-later AND ISC AND OpenSSL AND (MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-only)
@@ -413,6 +413,8 @@ Patch351: chromium-117-mnemonic-error.patch
 # https://bugs.chromium.org/p/chromium/issues/detail?id=1145581#c60
 # Disable BTI until this is fixed upstream.
 Patch352: chromium-117-workaround_for_crash_on_BTI_capable_system.patch
+# enable fstack-protector-strong
+Patch353: chromium-119-fstack-protector-strong.patch
 
 # upstream patches
 # revert due to build error redefine ATSPI version macros
@@ -1025,6 +1027,7 @@ udev.
 %patch -P352 -p1 -b .workaround_for_crash_on_BTI_capable_system
 %endif
 
+%patch -P353 -p1 -b .fstack-protector-strong
 %patch -P400 -p1 -R -b .revert-dont-redefine-ATSPI-version-macros.patch
 %patch -P401 -p1 -b .nullptr_t-without-namespace-std
 %patch -P402 -p1 -b .nvidia-use-separate-bo-to-verify-modifiers
@@ -1712,6 +1715,9 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
 %{chromium_path}/chromedriver
 
 %changelog
+* Sat Dec 02 2023 Than Ngo <than@redhat.com> - 119.0.6045.199-2
+- enable build flag -fstack-protector-strong for improved security
+
 * Wed Nov 29 2023 Than Ngo <than@redhat.com> - 119.0.6045.199-1
 - update to 119.0.6045.199
 

                 reply	other threads:[~2026-08-07 16:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178611874638.1.2803746009515768765.rpms-chromium-88b401e09e62@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox