From: Russell Coker <russell@coker.com.au>
To: forrest whitcher <fw@fwsystems.com>, selinux@tycho.nsa.gov
Cc: openafs-info@openafs.org
Subject: Re: selinux afs domain v 0.2
Date: Tue, 21 Jan 2003 03:01:38 +0100 [thread overview]
Message-ID: <200301210301.38254.russell@coker.com.au> (raw)
In-Reply-To: <20030120200718.57f30b5f.fw@fwsystems.com>
On Tue, 21 Jan 2003 02:07, forrest whitcher wrote:
> types/file.te: #afsd needs to write
> /usr/etc/openafs/AFSLog
>
> # usr_etc_log_t is created primarily for afsd which
> # wants to keep a log in /usr/etc/openafs
>
> type usr_etc_log_t, file_type, sysadmfile;
This is a really bad name.
Firstly your AFS package is broken. It should not put logs under an "etc"
directory, and even having /usr/etc is bad enough. I suggest recompiling
your AFS to put the logs in /var/log/afs* .
Then just do:
log_domain(afsd)
Also look at the rw_dir_create_file() macro and the use of { type types ... }
for specifying the types of files and directories, using those methods you
can significantly reduce the size of your policy file without changing the
result.
--
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
--
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:[~2003-01-21 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 1:07 selinux afs domain v 0.2 forrest whitcher
2003-01-21 2:01 ` Russell Coker [this message]
[not found] ` <20030121094847.A6403@informatik.tu-chemnitz.de>
2003-03-17 20:41 ` [OpenAFS] " forrest whitcher
2003-03-17 22:05 ` Russell Coker
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=200301210301.38254.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=fw@fwsystems.com \
--cc=openafs-info@openafs.org \
--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.