From: Russell Coker <rcoker@redhat.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux list <selinux@tycho.nsa.gov>,
Stephen Smalley <sds@epoch.ncsc.mil>
Subject: Re: Ok, I know this has been asked before, but why is there an ls_exec_t?
Date: Tue, 23 Nov 2004 09:10:12 +1100 [thread overview]
Message-ID: <1101161412.30097.85.camel@aeon> (raw)
In-Reply-To: <41A24D29.1010000@redhat.com>
ls_exec_t is for ftpd. But as ftp servers seem to either be moving in
the direction of minimal functionality and ls being built in or of
maximum functionality which includes automatically running tar and gzip
it seems that this isn't providing much benefit.
On Mon, 2004-11-22 at 15:33 -0500, Daniel J Walsh wrote:
> Is there really a good reason for hostname_exec_t?
Yes, it means that we can reduce the access granted to initrc_t. But if
you have unlimitedRC then it provides no benefit.
--
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:[~2004-11-22 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 20:33 Ok, I know this has been asked before, but why is there an ls_exec_t? Daniel J Walsh
2004-11-22 22:10 ` Russell Coker [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=1101161412.30097.85.camel@aeon \
--to=rcoker@redhat.com \
--cc=dwalsh@redhat.com \
--cc=sds@epoch.ncsc.mil \
--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.