From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 2/2] fcaps.eclass: make binaries readable by default
Date: Sun, 10 Nov 2024 17:38:22 -0500 [thread overview]
Message-ID: <a5a431a9-a6a3-4f71-9e66-94c85b16dca0@gentoo.org> (raw)
In-Reply-To: <20241110215401.128418-2-floppym@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 2106 bytes --]
On 11/10/24 4:54 PM, Mike Gilbert wrote:
> Removing the read bit from suid binaries has questionable security
> benefit, and may cause problems for some software.
>
> Users may override FCAPS_CAPS_MODE and FCAPS_NOCAPS_MODE should they
> desire the old behavior.
>
> Bug: https://bugs.gentoo.org/938164
> Signed-off-by: Mike Gilbert <floppym@gentoo.org>
> ---
> eclass/fcaps.eclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/eclass/fcaps.eclass b/eclass/fcaps.eclass
> index bf05776ba760..da4a52099396 100644
> --- a/eclass/fcaps.eclass
> +++ b/eclass/fcaps.eclass
> @@ -70,13 +70,13 @@ esac
> # @USER_VARIABLE
> # @DESCRIPTION:
> # Mode to use when capabilities are supported.
> -: ${FCAPS_CAPS_MODE:=0711}
> +: ${FCAPS_CAPS_MODE:=0755}
Considering the context of the linked bug, and the change offered here,
I don't really understand the proposed solution.
This is a very flexible variable. Way too flexible. There is no valid
use case for setting it to anything other than removing read
permissions, or preserving read permissions -- so why is it acceptable
to offer users the opportunity to define
FCAPS_CAPS_MODE="4123"
FCAPS_NOCAPS_MODE="0644"
Which is an error condition?
If we want a user variable at all here, let it be
: ${FCAPS_DENY_WORLD_READ:=no}
But I'm not convinced any optionality is necessary at all here. If the
expected behavior is to have read, and users are free to toggle sfperms
at the portage level, why is it necessary to make this additionally
configurable as an eclass variable?
Either way, there is also a stale comment in the function body:
# If everything goes well, we don't want the file to be readable
# by people.
> # @ECLASS_VARIABLE: FCAPS_NOCAPS_MODE
> # @USER_VARIABLE
> # @DESCRIPTION:
> # Mode to use when capabilities are not supported.
> -: ${FCAPS_NOCAPS_MODE:=4711}
> +: ${FCAPS_NOCAPS_MODE:=4755}
>
> # @FUNCTION: fcaps
> # @USAGE: [-o <owner>] [-g <group>] [-m <mode>] [-M <caps mode>] <capabilities> <file[s]>
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-11-10 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 21:54 [gentoo-dev] [PATCH 1/2] fcaps.eclass: introduce FCAPS_CAPS_MODE and FCAPS_NOCAPS_MODE Mike Gilbert
2024-11-10 21:54 ` [gentoo-dev] [PATCH 2/2] fcaps.eclass: make binaries readable by default Mike Gilbert
2024-11-10 22:38 ` Eli Schwartz [this message]
2024-11-11 0:14 ` Mike Gilbert
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=a5a431a9-a6a3-4f71-9e66-94c85b16dca0@gentoo.org \
--to=eschwartz@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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