From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Two issues with restorecon
Date: Tue, 29 Mar 2011 09:56:57 -0400 [thread overview]
Message-ID: <4D91E529.1090700@redhat.com> (raw)
In-Reply-To: <20110328221420.GG15708@hardeman.nu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/28/2011 06:14 PM, David H?rdeman wrote:
> On Fri, Feb 04, 2011 at 08:55:04AM -0500, Daniel J Walsh wrote:
>> On 02/04/2011 08:14 AM, David H?rdeman wrote:
>>> Two related issues I just discovered with restorecon (sorry, I'm not close
>>> to my private laptop so I can't provide patches):
>>>
>>> 1) When running "restorecon -r /", restorecon (setfiles) wants to write an
>>> audit message that the whole fs is being relabeled (only happens when doing
>>> it on /), but the refpolicy doesn't seem to give setfiles_t access to write
>>> audit messages which I guess it should.
>>>
>>> 2) When running "restorecon -r -n /", restorecon (setfiles) wants to write
>>> the same audit message as above - which would be misleading since it's not
>>> actually changing any labels.
>>>
>> Could you open two bugzillas
>
> I'm sorry, you got me confused...bugzilla entries in the redhat bugzilla
> database? I'm not a redhat user... (and apologies for not replying
> straight away)...
>
Yes I was thinking the Red Hat bugzilla, but now that you mention it, we
do allow the first in Red Hat/Fedora policy and the second is a bug in
policycoreutils/restorecon. (But not sure whether I would say it is a
high priority.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk2R5SkACgkQrlYvE4MpobPOxwCgraDPXrKFxeGc+EDftq5kg5Jm
vFgAoLzNaNLJBUAJswIbWdL3itkqlOfL
=fTxr
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-03-29 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:14 [refpolicy] Two issues with restorecon David Härdeman
2011-02-04 13:55 ` Daniel J Walsh
2011-03-28 22:14 ` David Härdeman
2011-03-29 13:56 ` 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=4D91E529.1090700@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.com \
/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.