From: Tom <tom@lemuria.org>
To: Russell Coker <russell@coker.com.au>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: pxe, tftpd and rsync policies
Date: Fri, 23 May 2003 10:08:27 +0200 [thread overview]
Message-ID: <20030523100827.L26001@lemuria.org> (raw)
In-Reply-To: <200305230243.32308.russell@coker.com.au>; from russell@coker.com.au on Fri, May 23, 2003 at 02:43:32AM +1000
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.
prev parent reply other threads:[~2003-05-23 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 13:48 pxe, tftpd and rsync policies Tom
2003-05-22 16:43 ` Russell Coker
2003-05-23 8:08 ` Tom [this message]
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=20030523100827.L26001@lemuria.org \
--to=tom@lemuria.org \
--cc=russell@coker.com.au \
--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.