From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: We currently have a problem with cp -a /media/cdrom /etc
Date: Fri, 12 Jan 2007 13:46:11 -0500 [thread overview]
Message-ID: <45A7D773.8040800@redhat.com> (raw)
Currently in policy we do NOT have the following rule
allow iso9660_t fs_t:filesystem associate;
This causes cp -a to blow up when copying a cdrom to ext3. I notice in
policy we do allow this for nfs_t and dosfs_t to be assicoated with fs_t.
So this causes two problems, if we use cp -a from nfs_t or dosfs_t we
end up with files on local disk labeled as nfs_t/dosfs_t when I believe
we would be better off if they had transitioned. So I could change
policy to similarly allow iso9660_t files to be created and fix the cp
-a problem.
Or I could remove the nfs_t and dosfs_t association and make the cp -a
problem worse. Since cp -a gets permission denied it really has no way
of knowing what the correct behavior should be.
Maybe a fix would be to allow cp to ask the kernel what to do if it can
not setfscreatecon a particular context on a file system.
Thoughts?
Dan
--
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 reply other threads:[~2007-01-12 18:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 18:46 Daniel J Walsh [this message]
2007-01-12 18:55 ` We currently have a problem with cp -a /media/cdrom /etc Stephen Smalley
2007-01-12 20:10 ` James Antill
2007-01-12 20:24 ` Stephen Smalley
2007-01-12 20:29 ` Stephen Smalley
2007-01-12 22:29 ` Casey Schaufler
2007-01-13 9:13 ` Russell Coker
2007-01-13 20:01 ` Casey Schaufler
2007-01-12 21:15 ` James Antill
2007-01-12 21:19 ` Stephen Smalley
2007-01-13 10:05 ` Jim Meyering
2007-01-15 5:16 ` James Antill
2007-01-15 7:54 ` Jim Meyering
2007-01-16 13:33 ` Stephen Smalley
2007-01-13 10:55 ` Russell Coker
2007-01-12 21:01 ` Stephen Smalley
2007-01-12 21:29 ` Jim Meyering
2007-01-12 21:19 ` Jim Meyering
2007-01-12 21:21 ` Stephen Smalley
2007-01-12 21:47 ` Jim Meyering
2007-01-12 21:56 ` Stephen Smalley
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=45A7D773.8040800@redhat.com \
--to=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.