public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] useless set*id binaries
Date: Fri, 27 Jan 2012 21:14:37 -0500	[thread overview]
Message-ID: <201201272114.37584.vapier@gentoo.org> (raw)
In-Reply-To: <4F23543D.60601@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1134 bytes --]

On Friday 27 January 2012 20:49:49 Samuli Suominen wrote:
> and people have multiple times tried to convince the cdrtools author to
> change this, but without success.
> the author can be, well, ...

sure, i'm not expecting him to be anything resembling reasonable.  but if we 
can reduce set*id impact by default and that means carrying a custom patch, i 
think that's OK.

i thought we used to have set*id USE flags, but maybe all the packages with it 
have migrated away.

my proposal would be to add a patch to ignore EACCES just like it already does 
for ENOENT.  then add a setuid USE flag that'd give the behavior we have today 
(disabled by default) for the binaries that do writing.  the ones that only 
read have no excuse for needing setuid.  then if the user has built with USE=-
setuid, we elog a message like:
	you've built with USE=-setuid.  that means in order to access
	your discs, you need to add yourself to the cdrom group.
	if your burning does not go well, you can try adding the cdrom
	group to limits.conf with rtprio/mlock access like so:
		<snippets for people to copy & paste>
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-01-28  2:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28  0:14 [gentoo-dev] useless set*id binaries Mike Frysinger
2012-01-28  0:18 ` Samuli Suominen
2012-01-28  0:41   ` Mike Frysinger
2012-01-28  1:07     ` Samuli Suominen
2012-01-28  1:49       ` Mike Frysinger
2012-01-28  1:49         ` Samuli Suominen
2012-01-28  2:14           ` Mike Frysinger [this message]
2012-01-28  6:28           ` Ulrich Mueller
2012-01-28  7:19             ` Samuli Suominen
2012-01-28  8:15               ` Ulrich Mueller
2012-01-28  8:32       ` Michał Górny
2012-01-28  8:35         ` Samuli Suominen
2012-01-28  1:28 ` Chí-Thanh Christopher Nguyễn
2012-01-28  1:54   ` Mike Frysinger

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=201201272114.37584.vapier@gentoo.org \
    --to=vapier@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