From: Michael C Thompson <thompsmc@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: [PATCH 3/4] newrole suid functionality (take 2)
Date: Thu, 02 Nov 2006 11:22:46 -0600 [thread overview]
Message-ID: <454A2966.5050702@us.ibm.com> (raw)
In-Reply-To: <1161630359.3316.127.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Tue, 2006-10-17 at 13:42 -0500, Michael C Thompson wrote:
>> Michael C Thompson wrote:
>>> This is the intro to a set of four patches.
>>>
>>> These patches are an attempt to make newrole be an acceptably secure
>>> suid root program, to provide it with the capabilities to generate audit
>>> records (existing) and handle polyinstatiation (new).
>>>
>>> The 4 patches are as follows:
>>> 1) New functions introduced to newrole.c, new and existing functionality
>>> 2) Changes to existing functions in newrole.c
>>> 3) Updates to main in newrole.c to use the aforementioned changes
>> This is the 3rd of 4 patches.
>> This patch applies against policycoreutils-1.30.30-1.
>>
>> Changes:
>> * main is changed in the following ways:
>> - remove the duplicated functionality from patch 1/4
>> - set to call the new functions from patch 1/4
>> - set to use changes to functions in patch 2/4
>> - introduces better error handling and cleanup paths
>>
>> Signed-off-by: Michael Thompson <thompsmc@us.ibm.com>
>
> diff -Naur policycoreutils-1.30.30.orig/newrole/newrole.c policycoreutils-1.30.30.suid/newrole/newrole.c
> --- policycoreutils-1.30.30.orig/newrole/newrole.c 2006-10-17 13:15:20.000000000 -0500
> +++ policycoreutils-1.30.30.suid/newrole/newrole.c 2006-10-17 13:15:03.000000000 -0500
> @@ -897,47 +898,43 @@
>
> int main(int argc, char *argv[])
> <snip>
> + /*
> + * Step 0: Setup
> + *
> + * Do some intial setup, including dropping capabilities, checking
> + * if it makes sense to continue to run newrole, and setting up
> + * a scrubbed environment.
> + */
> + if (set_signal_handles())
> + return -1;
> + if (drop_capabilities())
> + return -1;
>
> I'd keep drop_capabilities() first, as it was before this patch.
> It would also make sense to move up sanitize_environment() as soon as
> possible, even if that means splitting it into two phases (in particular
> considering the locale support).
Would this order be acceptable?
drop_cap
set_signal_handlers
setlocale
sanitize_env
...
I'm not familiar with locale enough to understand your point above, but
I imagine doing environ = NULL will mess up the locale, but I am not
sure. If that is right, we need to do it before we sanitize the
environment, right?
Thanks,
Mike
--
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:[~2006-11-02 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 18:24 [PATCH 0/4] newrole suid functionality (take 2) Michael C Thompson
2006-10-17 18:38 ` [PATCH 1/4] " Michael C Thompson
2006-10-17 18:40 ` [PATCH 0/4] " Michael C Thompson
2006-10-17 18:42 ` [PATCH 3/4] " Michael C Thompson
2006-10-23 19:05 ` Stephen Smalley
2006-10-23 19:29 ` Michael C Thompson
2006-11-02 17:22 ` Michael C Thompson [this message]
2006-11-02 18:34 ` Stephen Smalley
2006-11-02 20:35 ` Michael C Thompson
2006-11-02 20:54 ` Stephen Smalley
2006-11-02 21:38 ` Michael C Thompson
2006-10-17 18:43 ` [PATCH 4/4] " Michael C Thompson
2006-10-23 19:09 ` Stephen Smalley
2006-10-23 19:30 ` Michael C Thompson
2006-10-23 18:56 ` [PATCH 0/4] " Stephen Smalley
2006-10-23 19:26 ` Michael C Thompson
2006-11-02 17:18 ` Michael C Thompson
2006-11-02 18:21 ` Stephen Smalley
2006-11-02 18:38 ` Michael C Thompson
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=454A2966.5050702@us.ibm.com \
--to=thompsmc@us.ibm.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.