mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "willy tarreau" <wtarreau@yahoo.fr>
To: eric@sparrow.nad.adelphia.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: capabilities carried over execve()
Date: Tue, 24 Apr 2001 17:05:46 +0200 (CEST)	[thread overview]
Message-ID: <20010424150546.6917.qmail@web1103.mail.yahoo.com> (raw)

I personnaly use this simple patch which allows me
to keep caps over execve(). It allows me to give a
few more rights to some trusted users, such as 
kill, insmod... without risking unlink, chown or 
so. I couldn't find any other way to achieve this.

If needed, I can send you the complete prog which
sets the requested capabilities upon login, 
eventually asking for a password and limited in 
time of day.

Regards,
Willy

--- linux-2.2.18-wt11/fs/exec.c Fri Feb 16 23:11:52
2001
+++ linux-2.2.18-wt11+caps/fs/exec.c    Thu Feb 22
20:45:33 2001
@@ -702,7 +702,10 @@
        cap_clear(bprm->cap_inheritable);
        cap_clear(bprm->cap_permitted);
        cap_clear(bprm->cap_effective);
-
+/*** FIXME: just a test : keep permitted and
effective ******/
+bprm->cap_permitted =
cap_intersect(current->cap_inheritable,current->cap_permitted);
+bprm->cap_effective =
cap_intersect(current->cap_inheritable,current->cap_effective);
+/*** /FIXME ****/
        /*  To support inheritance of root-permissions
and suid-root
          *  executables under compatibility mode, we
raise all three
          *  capability sets for the file.



___________________________________________________________
Do You Yahoo!? -- Pour faire vos courses sur le Net, 
Yahoo! Shopping : http://fr.shopping.yahoo.com

             reply	other threads:[~2001-04-24 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 15:05 willy tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24 14:45 Eric Buddington
2001-04-26 20:10 ` Pavel Machek

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=20010424150546.6917.qmail@web1103.mail.yahoo.com \
    --to=wtarreau@yahoo.fr \
    --cc=eric@sparrow.nad.adelphia.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®