From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: policy mods for xfs (to support xfstt and xfs-xtt)
Date: Wed, 25 Aug 2004 21:24:12 +1000 [thread overview]
Message-ID: <200408252124.12152.russell@coker.com.au> (raw)
In-Reply-To: <20040823232812.GB12720@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
What is /usr/bin/xfs-xtt? Contents-i386.gz doesn't list it.
+allow xfs_t { etc_runtime_t }:dir { getattr search };
There should not be a directory of type etc_runtime_t (there is no
file_contexts entry for it).
What is /var/cache/xfstt? The name implies that xfs would write to it, in
which case fonts_t is not the appropriate type label. Changing the policy to
allow xfs_t to write to fonts_t changes the way things work. I think that we
probably need different types for read-only files and writable files.
I've put a few things from your patch in my tree and attached the relevant
files in a tgz so we can work from the same base.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
[-- Attachment #2: xfs.tgz --]
[-- Type: application/x-tgz, Size: 4599 bytes --]
next prev parent reply other threads:[~2004-08-25 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 23:28 policy mods for xfs (to support xfstt and xfs-xtt) Luke Kenneth Casson Leighton
2004-08-25 11:24 ` Russell Coker [this message]
2004-08-25 13:28 ` Luke Kenneth Casson Leighton
2004-08-25 22:16 ` Erich Schubert
2004-08-26 11:00 ` Luke Kenneth Casson Leighton
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=200408252124.12152.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=lkcl@lkcl.net \
--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.