public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alon Bar-Lev" <alonbl@gentoo.org>
To: "Mike Frysinger" <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [SECURITY] Minimizing the suid usage
Date: Mon, 24 Mar 2008 15:55:48 +0200	[thread overview]
Message-ID: <9e0cf0bf0803240655g6f0ab2dbh3782fd63222287b8@mail.gmail.com> (raw)
In-Reply-To: <200803240953.52578.vapier@gentoo.org>

On 3/24/08, Mike Frysinger <vapier@gentoo.org> wrote:
>  how much do we want to help the user ?  if they have USE=filecaps, then dont
>  perform any checking ?  we'll need a kernel with file capabilities turned on,
>  otherwise the prog wont work unless it's setuid ... so do we perform checking
>  and drop the setuid bit on the post sly ?  i'd prefer we just make the
>  filecaps desc verbose: dont set this unless you have new enough kernel with
>  options enabled, otherwise things may stop working properly as non-root.

I also prefer descriptive warning and not runtime checks. Worse case
scenario, system will be usable for root only. root can remove this
USE flag and emerge --update --deep --newuse world.

Alon.
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-24 13:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 18:21 [gentoo-dev] [SECURITY] Minimizing the suid usage Alon Bar-Lev
2008-03-23 18:26 ` Ciaran McCreesh
2008-03-23 18:30   ` Alon Bar-Lev
2008-03-23 18:34     ` Ciaran McCreesh
2008-03-23 18:45       ` Alon Bar-Lev
2008-03-23 22:02         ` Ciaran McCreesh
2008-04-01 10:50         ` Ciaran McCreesh
2008-03-24 11:50 ` Mike Frysinger
2008-03-24 12:27   ` Alon Bar-Lev
2008-03-24 13:20     ` Ciaran McCreesh
2008-03-24 13:53     ` Mike Frysinger
2008-03-24 13:55       ` Alon Bar-Lev [this message]
2008-08-05  8:51 ` Bruno Prémont
2008-08-05  8:54   ` Ciaran McCreesh
2009-01-01 12:23     ` Bruno

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=9e0cf0bf0803240655g6f0ab2dbh3782fd63222287b8@mail.gmail.com \
    --to=alonbl@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=vapier@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