From: Tom <tom@lemuria.org>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: pxe, tftpd and rsync policies
Date: Thu, 22 May 2003 15:48:22 +0200 [thread overview]
Message-ID: <20030522154816.C6588@lemuria.org> (raw)
I'm currently trying to write policies for a pxe daemon, tftpd and
rsync run as a daemon. This is part of a system imager server that I'm
installing at work. The background is that an image server definitely
needs to be trustworthy.
That might not mesh very well with tftpd and rsync at first glance, but
that is a different problem.
The relationship between pxe and tftpd is pretty close. I was thinking
of merging them into one policy, in fact. Likewise, rsync is used
slightly customized in this setting, and will need new file types and
access rules just for system imager operation.
I'm looking for input on how to organize this policy. So far, I've
edited the tftpd policy and written new ones for rsync and pxe. I will
also have to write policies for the system imager tool set.
On the other hand, I could merge all these changes into one
systemimager policy. But then this policy would overlap in part with
other policies (currently just tftpd, but who says there won't be an
rsync or pxe policy one day?).
I could also write a systemimager.te for the tools and sprinkle
ifdef(`systemimager.te' throughout the other policies - but do we
really want to fill policies with dozens of "if this special package is
being used..." ?
What's the preferred approach here?
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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:[~2003-05-22 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 13:48 Tom [this message]
2003-05-22 16:43 ` pxe, tftpd and rsync policies Russell Coker
2003-05-23 8:08 ` Tom
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=20030522154816.C6588@lemuria.org \
--to=tom@lemuria.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.