From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <SELinux@tycho.nsa.gov>,
RH SELinux list <rhselinux-list@redhat.com>
Subject: Re: mv and cp behavior.
Date: Sat, 16 Oct 2004 20:57:53 +0100 [thread overview]
Message-ID: <20041016195753.GD19398@lkcl.net> (raw)
In-Reply-To: <41712EEF.9090402@redhat.com>
On Sat, Oct 16, 2004 at 10:23:43AM -0400, Daniel J Walsh wrote:
> I believe that the what mv/cp is doing is wrong and we could do better,
> by default.
after (funnily enough) just examining apache_macros.te, i don't see a
file_auto_trans in there which i would have expected there to be.
sure, there's a create_dir_file, but i would have expected at least to
see some use of file_type_auto_trans($1_t, httpd_$1_content_t, httpd_$1_content_t)
[i think that's right: if a user creates stuff in the
httpd_user_content_t directory, it's given that same context]
and yes i'd expect mv and cp to obey that file_type_auto_trans.
l.
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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:[~2004-10-16 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 14:23 mv and cp behavior Daniel J Walsh
2004-10-16 19:57 ` Luke Kenneth Casson Leighton [this message]
2004-10-18 13:18 ` Stephen Smalley
2004-10-18 16:07 ` Colin Walters
2004-10-18 17:14 ` Stephen Smalley
2004-10-18 17:43 ` Colin Walters
2004-10-18 18:22 ` Erich Schubert
2004-10-18 20:24 ` Colin Walters
2004-10-24 23:40 ` Nifty Hat Mitch
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=20041016195753.GD19398@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=rhselinux-list@redhat.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.