From: Stephen Smalley <sds@epoch.ncsc.mil>
To: ivg2@cornell.edu
Cc: Daniel J Walsh <dwalsh@redhat.com>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Updated policy
Date: Thu, 27 Jan 2005 10:50:36 -0500 [thread overview]
Message-ID: <1106841036.28623.128.camel@moss-spartans.epoch.ncsc.mil> (raw)
In-Reply-To: <1106727722.17956.3.camel@cobra.ivg2.net>
On Wed, 2005-01-26 at 03:22, Ivan Gyurdiev wrote:
> On Tue, 2005-01-25 at 14:56 -0500, Daniel J Walsh wrote:
> > Many changes to allow policy to support telnetd, rlogind and rshd.
> >
> > allow mount_t binfmt_misc_fs_t:dir mounton;
> > Required to run wine.
>
> Now there is:
>
> allow mount_t binfmt_misc_fs_t:dir mounton;
> ...
> # mount binfmt_misc on /proc/sys/fs/binfmt_misc
> allow mount_t sysctl_t:dir { mounton search };
>
> Are both of those necessary?
Shouldn't be. mounton permission is required to the mount point
directory, which should be sysctl_t. binfmt_misc_fs_t should only be on
the mounted directory. Duplicate mount?
--
Stephen Smalley <sds@epoch.ncsc.mil>
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:[~2005-01-27 15:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 19:56 Updated policy Daniel J Walsh
2005-01-25 21:56 ` Ivan Gyurdiev
2005-01-26 10:57 ` Ivan Gyurdiev
2005-01-26 12:35 ` Stephen Smalley
2005-01-26 12:18 ` Stephen Smalley
2005-01-26 6:54 ` Ivan Gyurdiev
2005-01-26 8:22 ` Ivan Gyurdiev
2005-01-27 15:50 ` Stephen Smalley [this message]
2005-01-27 15:57 ` Stephen Smalley
2005-01-27 16:30 ` Daniel J Walsh
2005-01-27 16:45 ` Daniel J Walsh
2005-01-27 16:22 ` Stephen Smalley
2005-01-27 16:33 ` Daniel J Walsh
2005-01-27 17:27 ` Ivan Gyurdiev
2005-12-10 5:26 Daniel J Walsh
2005-12-13 19:51 ` Christopher J. PeBenito
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=1106841036.28623.128.camel@moss-spartans.epoch.ncsc.mil \
--to=sds@epoch.ncsc.mil \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
/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.