From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP]: hooks/post-install: add check setuid/setgid hook
Date: Sun, 03 Apr 2022 00:09:15 +0200 [thread overview]
Message-ID: <20220402220915.6vcxPqGV2DYugQivtz-kdgXUNDGCkk73abVN4hSOKEA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33011@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
There is an updated pull request by paper42 against master on the void-packages repository
https://github.com/paper42/void-packages setuid-setgid-hook
https://github.com/void-linux/void-packages/pull/33011
[WIP]: hooks/post-install: add check setuid/setgid hook
Closes #32156
cc @ericonr
A patch file from https://github.com/void-linux/void-packages/pull/33011.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-setuid-setgid-hook-33011.patch --]
[-- Type: text/x-diff, Size: 2039 bytes --]
From 5454e6404159f662c3ef289210b6d4f859fcaff9 Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sat, 18 Sep 2021 13:42:00 +0200
Subject: [PATCH 1/2] hooks/post-install: add check setuid/setgid hook
---
.../post-install/15-check-setuid-setgid.sh | 26 +++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 common/hooks/post-install/15-check-setuid-setgid.sh
diff --git a/common/hooks/post-install/15-check-setuid-setgid.sh b/common/hooks/post-install/15-check-setuid-setgid.sh
new file mode 100644
index 000000000000..3e864cb24c91
--- /dev/null
+++ b/common/hooks/post-install/15-check-setuid-setgid.sh
@@ -0,0 +1,26 @@
+dofind() {
+ error=
+ for setidfile in $(find "$PKGDESTDIR" -type f -perm -"$1"); do
+ matched=
+ for allowed_file in $(eval "echo \${$2}"); do
+ if [ "$PKGDESTDIR$allowed_file" = "$setidfile" ]; then
+ matched=y
+ break
+ fi
+ done
+ if [ -n "$matched" ]; then
+ echo "$2 file: ${setidfile#$PKGDESTDIR}"
+ else
+ msg_red "not allowed $2 file: ${setidfile#$PKGDESTDIR}\n"
+ error=y
+ fi
+ done
+ if [ -n "$error" ]; then
+ msg_error "$2 files not explicitly allowed, please list them in \$$2\n"
+ fi
+}
+
+hook() {
+ dofind 4000 setuid
+ dofind 2000 setgid
+}
From 0a2b7cd99661b3ea9e9a243442cfc3cec4cccd12 Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sat, 18 Sep 2021 14:10:00 +0200
Subject: [PATCH 2/2] opendoas: explicitly allow setuid
---
srcpkgs/opendoas/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/opendoas/template b/srcpkgs/opendoas/template
index 685cd45da59b..8ce229503c2e 100644
--- a/srcpkgs/opendoas/template
+++ b/srcpkgs/opendoas/template
@@ -14,6 +14,7 @@ license="ISC, BSD-3-Clause"
homepage="https://github.com/Duncaen/OpenDoas"
distfiles="https://github.com/Duncaen/OpenDoas/archive/v${version}.tar.gz"
checksum=6da058a0e70b7543bc60624389b0b00b686189ec933828c522bf8b2600495a67
+setuid="/usr/bin/doas"
build_options="pam timestamp"
build_options_default="pam timestamp"
next prev parent reply other threads:[~2022-04-02 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 12:10 [PR PATCH] " paper42
2022-04-02 22:09 ` paper42 [this message]
2022-04-03 3:59 ` [WIP]: " 0x5c
2022-04-03 4:00 ` 0x5c
2022-04-03 15:57 ` [PR REVIEW] " Duncaen
2022-04-04 4:06 ` 0x5c
2022-04-04 4:12 ` 0x5c
2022-04-04 4:13 ` 0x5c
2022-04-06 17:45 ` paper42
2022-04-06 17:54 ` [PR PATCH] [Updated] " paper42
2022-04-20 1:39 ` [PR REVIEW] " 0x5c
2022-04-20 2:07 ` 0x5c
2022-04-20 19:19 ` 0x5c
2022-04-20 19:49 ` 0x5c
2022-04-20 21:21 ` 0x5c
2022-05-30 20:27 ` [PR PATCH] [Updated] " paper42
2023-02-25 11:23 ` paper42
2023-02-25 11:30 ` paper42
2023-08-07 0:40 ` [PR PATCH] [Updated] " classabbyamp
2023-09-20 13:29 ` 0x5c
2023-09-20 13:29 ` 0x5c
2023-09-20 13:41 ` 0x5c
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=20220402220915.6vcxPqGV2DYugQivtz-kdgXUNDGCkk73abVN4hSOKEA@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).