public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kalev Lember <klember@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Don't use full path for triggers
Date: Tue, 11 Aug 2026 10:36:19 GMT [thread overview]
Message-ID: <178644457907.1.3200252051350515085.rpms-glib2-801e4a1ba04b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 801e4a1ba04ba8ce75c047e21a8df11ab59bf8b3
Author : Kalev Lember <klember@redhat.com>
Date : 2017-03-20T11:06:22+01:00
Stats : +4/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/801e4a1ba04ba8ce75c047e21a8df11ab59bf8b3?branch=cve-2026-58016-f44
Log:
Don't use full path for triggers
rpm already sets a sufficiently narrow PATH for all scripts and there's
no need to further confine them.
---
diff --git a/glib2.spec b/glib2.spec
index 9531ff6..5847e12 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -133,16 +133,16 @@ chmod 644 $RPM_BUILD_ROOT%{_datadir}/bash-completion/completions/*
%postun -p /sbin/ldconfig
%transfiletriggerin -- %{_libdir}/gio/modules
-/bin/gio-querymodules-%{__isa_bits} %{_libdir}/gio/modules &> /dev/null || :
+gio-querymodules-%{__isa_bits} %{_libdir}/gio/modules &> /dev/null || :
%transfiletriggerpostun -- %{_libdir}/gio/modules
-/bin/gio-querymodules-%{__isa_bits} %{_libdir}/gio/modules &> /dev/null || :
+gio-querymodules-%{__isa_bits} %{_libdir}/gio/modules &> /dev/null || :
%transfiletriggerin -- %{_datadir}/glib-2.0/schemas
-/bin/glib-compile-schemas %{_datadir}/glib-2.0/schemas &> /dev/null || :
+glib-compile-schemas %{_datadir}/glib-2.0/schemas &> /dev/null || :
%transfiletriggerpostun -- %{_datadir}/glib-2.0/schemas
-/bin/glib-compile-schemas %{_datadir}/glib-2.0/schemas &> /dev/null || :
+glib-compile-schemas %{_datadir}/glib-2.0/schemas &> /dev/null || :
%files -f glib20.lang
%license COPYING
reply other threads:[~2026-08-11 10:36 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=178644457907.1.3200252051350515085.rpms-glib2-801e4a1ba04b@fedoraproject.org \
--to=klember@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