From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] explicitly allow setuid and setgid permissions in templates
Date: Fri, 23 Jul 2021 16:03:31 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32156@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
New issue by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/32156
Description:
There are no checks for setuid and setgid permissions right now which could potentially be a security risk.
a) `setugid=yes` allows both setuid and setgid permissions in all files in the package
b) `setugid="usr/bin/su"` per-file rules
split setuid and setgid rules
c) `setuid=yes; setgid=yes`
d) `setuid="usr/bin/su"; setgid=""`
I will prepare a post-install hook when it's decided which method is preferred. I like c) the most, because there are some packages providing just setgid binaries without needing setuid (mlocate). b) and d) sound too verbose to me and if a package provides a set{u,g}id binary, the whole package is trusted.
I would also like to ask someone with access to the binary repository to post here which packages have set{u,g}id binaries.
cc @ericonr
next reply other threads:[~2021-07-23 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 14:03 paper42 [this message]
2021-07-23 14:35 ` ericonr
2021-07-26 12:10 ` fosslinux
2021-07-26 13:33 ` paper42
2021-07-26 13:33 ` paper42
2021-07-26 13:33 ` paper42
2021-07-27 16:13 ` Duncaen
2021-07-27 16:13 ` Duncaen
2021-07-27 17:42 ` ericonr
2022-05-30 2:15 ` github-actions
2022-08-17 1:48 ` CameronNemo
2022-08-17 2:43 ` ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32156@inbox.vuxu.org \
--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).