From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: A couple of patches to setfiles.
Date: Tue, 05 Oct 2004 14:51:59 -0400 [thread overview]
Message-ID: <4162ED4F.6000208@redhat.com> (raw)
In-Reply-To: <1097001163.3878.134.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Tue, 2004-10-05 at 14:24, Stephen Smalley wrote:
>
>
>>You want to log always? Should be based on an option, like the existing
>>verbose option, and you likely only want to log if !only_changed_user as
>>with the verbose case.
>>
>>
>
>Actually, there is already a -o option to log to a specified file. Why
>add syslog calls as well?
>
>
>
Steve Grub has pointed out that the way we are doing setfiles is all
wrong, and that we should be logging
to syslog. That way a management infrastructure could monitor and
manage the environment. Writing
temporary or log files in arbitrary places is wrong. Tools like
logrotate are going to clean them up. ETC.
So the -o flag should go and we should use syslog.
So I think we need to relook at setfiles/fixfiles and plug them better
into standard architecture.
I think we need a mechanism to tell us when a file actually has the
wrong context versus one that just does not
match the context in the file_context file. Russell pointed out that
the contents of the homedirectory should
not have an automatic tool looking at their context because it might
open up a security hole if you were to
arbitrarily clean up the false positives.
Dan
--
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:[~2004-10-05 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 11:29 A couple of patches to setfiles Daniel J Walsh
2004-10-05 18:24 ` Stephen Smalley
2004-10-05 18:32 ` Stephen Smalley
2004-10-05 18:51 ` Daniel J Walsh [this message]
2004-10-05 19:15 ` Stephen Smalley
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=4162ED4F.6000208@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@epoch.ncsc.mil \
/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.