From: Daniel J Walsh <dwalsh@redhat.com>
To: russell@coker.com.au
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Problems with fixfiles and setfiles.
Date: Wed, 29 Sep 2004 10:42:24 -0400 [thread overview]
Message-ID: <415AC9D0.1080708@redhat.com> (raw)
In-Reply-To: <200409300034.10552.russell@coker.com.au>
Russell Coker wrote:
>On Wed, 29 Sep 2004 06:11, Daniel J Walsh <dwalsh@redhat.com> wrote:
>
>
>>The fixfiles script is used to report and fix file contexts that are
>>invalid, the problem is that it gets a lot of
>>false positives. Reviewing fixfiles.cron shows that most of the files
>>created by mozilla are reported as invalid.
>>It would be nice if we could remove these false positives by some means.
>>
>>If we had some mechanism of saying a file could have one of several
>>valid contexts, or be in a context that
>>has a certain attribute.
>>
>>
>
>For files under the home directory the valid contexts are all the contexts
>that the user in question can create (directly or indirectly).
>
>If the user does "mv .ssh .ssh-old" we don't want .ssh-old relabelled at
>user_home_t.
>
>Maybe we should just have fixfiles skip the home directories?
>
>
>
Yes I considered that, but fixfiles is just a front end to setfiles,
which does not have an easy way of skipping home dirs.
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.
prev parent reply other threads:[~2004-09-29 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:11 Problems with fixfiles and setfiles Daniel J Walsh
2004-09-28 23:02 ` Luke Kenneth Casson Leighton
2004-09-29 14:34 ` Russell Coker
2004-09-29 14:42 ` Daniel J Walsh [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=415AC9D0.1080708@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=russell@coker.com.au \
/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.