From: James Antill <jantill@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Jim Meyering <jim@meyering.net>, selinux@tycho.nsa.gov
Subject: Re: does mv need a --context=CTX (-Z) option, too?
Date: Thu, 10 Aug 2006 12:18:46 -0400 [thread overview]
Message-ID: <1155226726.2496.14.camel@code.and.org> (raw)
In-Reply-To: <1155218058.1123.301.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Thu, 2006-08-10 at 09:54 -0400, Stephen Smalley wrote:
> Now, as far as preserving fscreate across execve goes, doing that in the
> case where there is no change in the current context of the task is
> conceivable (so no implications for letting the caller influence the
> program), although it would be a change in behavior that has been
> present for quite some time (and seems rather late to make it into e.g.
> RHEL5 or FC6). I have no strong opinion on that, but it could introduce
> unexpected behaviors; some programs today might be setting fscreate and
> exec'ing helpers while not expecting the helpers to pick up that
> fscreate context.
What about dynamic domain transitions? Eg.
task_A = *:foo_t
task_A calls setfscreatecon(*:bad_t)
fork() = task_B
task_B = *:foo_t
task_B calls setcon(*:bar_t)
task_B creates file
--
James Antill <jantill@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-08-10 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 10:13 does mv need a --context=CTX (-Z) option, too? Jim Meyering
2006-08-10 13:51 ` kmacmillan
2006-08-10 15:15 ` Jim Meyering
2006-08-10 16:00 ` James Antill
2006-08-10 16:01 ` Karl MacMillan
2006-08-10 17:39 ` Jim Meyering
2006-08-10 13:54 ` Stephen Smalley
2006-08-10 14:27 ` Jim Meyering
2006-08-10 14:41 ` Daniel J Walsh
2006-08-10 15:47 ` Casey Schaufler
2006-08-10 15:53 ` Daniel J Walsh
2006-08-10 16:01 ` Casey Schaufler
2006-08-10 16:03 ` Karl MacMillan
2006-08-10 17:35 ` Jim Meyering
2006-08-10 22:56 ` Russell Coker
2006-08-10 16:18 ` James Antill [this message]
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=1155226726.2496.14.camel@code.and.org \
--to=jantill@redhat.com \
--cc=jim@meyering.net \
--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.