pxe, tftpd and rsync policies

pxe, tftpd and rsync policies

[Tom]

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.

Re: pxe, tftpd and rsync policies

[Russell Coker]

On Thu, 22 May 2003 23:48, Tom wrote:
> I'm currently trying to write policies for a pxe daemon, tftpd and
> rsync run as a daemon.

For rsync I always run it over ssh, so rsync doesn't need any special 
permissions, the user that you are logging in as needs to be able to access 
the files appropriately.

As for PXE, I thought that someone had written a program that implemented both 
TFTP and PXE protocols...

> 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 think it's good to keep these things separate.  Some people will want to use 
them for different tasks.

> 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..." ?

Minimising use of ifdef is a good idea.

-- 
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.

Re: pxe, tftpd and rsync policies

[Tom]

On Fri, May 23, 2003 at 02:43:32AM +1000, Russell Coker wrote:
> For rsync I always run it over ssh, so rsync doesn't need any special 
> permissions, the user that you are logging in as needs to be able to access 
> the files appropriately.

I know. However, the ssh support of system imager is broken in the
3.0.1 version. At least that's what the guys I had set up the server
found out, they couldn't get it to work. rsync worked right away.

(as I said, that's a different story. :) )


> As for PXE, I thought that someone had written a program that implemented both 
> TFTP and PXE protocols...

That's one more argument to merge these two policies into one. I don't
see what harm it would do, even if only tftp is run, except for a few
unused policy rules.


-- 
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.