From: Stephen Smalley <sds@tycho.nsa.gov>
To: Xavier Toth <txtoth@gmail.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: problem with capabilities inheritance and auditing in python
Date: Thu, 05 Feb 2009 13:10:36 -0500 [thread overview]
Message-ID: <1233857436.3181.40.camel@localhost.localdomain> (raw)
In-Reply-To: <cadfc0e40902050908n5391c4b4l417714fe87a47f29@mail.gmail.com>
On Thu, 2009-02-05 at 11:08 -0600, Xavier Toth wrote:
> I've set the capabilities on a script that runs some python code with
> auditing calls in it but I'm not getting audit records written to the
> audit log. From what I've read I thought the +i would all the
> capability to be inherited across execve but this doesn't appear to be
> the case. Can anyone help me understand what's going wrong here? Is
> there a way in the python code to get the capabilities to see if
> indeed cap_audit_write was inherited?
Linux doesn't honor setuid on scripts, and file capabilities are
supposed to have the same behavior (they didn't for a while due to an
oversight, but that was corrected). You need an executable wrapper
program that invokes the script, like:
http://oss.tresys.com/projects/clip/browser/trunk/RHEL5.2/scripts/wrappers/wrapper.c
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-02-05 18:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 17:08 problem with capabilities inheritance and auditing in python Xavier Toth
2009-02-05 18:10 ` Stephen Smalley [this message]
2009-02-06 21:56 ` Xavier Toth
2009-02-09 14:02 ` Stephen Smalley
2009-02-09 16:42 ` Xavier Toth
2009-02-09 20:17 ` Stephen Smalley
2009-02-09 20:42 ` Serge E. Hallyn
2009-02-10 17:00 ` Xavier Toth
2009-02-10 18:34 ` Serge E. Hallyn
2009-02-10 20:20 ` Xavier Toth
2009-02-10 20:33 ` Stephen Smalley
2009-02-10 20:59 ` Xavier Toth
2009-02-10 21:08 ` Stephen Smalley
2009-02-10 21:30 ` Serge E. Hallyn
2009-02-10 21:38 ` Serge E. Hallyn
2009-02-10 21:45 ` Xavier Toth
2009-02-10 21:25 ` Stephen Smalley
2009-02-10 21:37 ` Xavier Toth
2009-02-10 21:38 ` Stephen Smalley
2009-02-10 21:46 ` Serge E. Hallyn
2009-02-10 21:44 ` Serge E. Hallyn
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=1233857436.3181.40.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.