All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [patch 1/3] Implementation of system conf type
Date: Wed, 02 Mar 2011 09:33:07 -0500	[thread overview]
Message-ID: <4D6E5523.7040001@tresys.com> (raw)
In-Reply-To: <1299012069.14035.36.camel@tesla.lan>

On 03/01/11 15:41, Guido Trentalancia wrote:
> On Tue, 01/03/2011 at 14.57 -0500, Christopher J. PeBenito wrote:
>> On 02/22/11 11:18, Guido Trentalancia wrote:
>>> On Tue, 22/02/2011 at 10.46 -0500, Christopher J. PeBenito wrote:
>>>> On 02/21/11 15:11, Guido Trentalancia wrote:
>>>>> On Mon, 21/02/2011 at 10.40 -0500, Daniel J Walsh wrote:
>>>>>> On 02/20/2011 12:37 AM, Guido Trentalancia wrote:
>>>> I don't understand why system-config-firewall would need to write to
>>>> etc_t, the iptables rules have their own labeling:
>>>>
>>>> /etc/sysconfig/ip6?tables.*     --
>>>> gen_context(system_u:object_r:iptables_conf_t,s0)
>>>> /etc/sysconfig/system-config-firewall.* --
>>>> gen_context(system_u:object_r:iptables_conf_t,s0)
>>>>
>>>>> Yes, this is very important. But isn't etc_runtime_t what is needed here
>>>>> then ?
>>>>
>>>> No, the purpose of that type is for generated files such as /.autofsck
>>>> and /etc/motd.
>>>
>>> Well then I think we need to check a few labels:
>>>
>>> /etc/smartd\.conf.*     --      system_u:object_r:etc_runtime_t:s0
>>> /etc/reader\.conf       --      system_u:object_r:etc_runtime_t:s0
>>
>> Right, these need to be reevaluated.
> 
> I suppose you are going to take care of that.

Dan/Miroslav, do you have any thoughts on this?  I think these lines and
the below four lines should be removed.

>>> And there is also other stuff that is not automatically-generated (if
>>> that is what you meant for "generated"):
>>>
>>> /etc/motd       --      system_u:object_r:etc_runtime_t:s0
>>> /etc/issue      --      system_u:object_r:etc_runtime_t:s0
>>> /etc/HOSTNAME   --      system_u:object_r:etc_runtime_t:s0
>>> /etc/issue\.net --      system_u:object_r:etc_runtime_t:s0
>>
>> These can be generated out of init scripts.  For example, Fedora used to
>> generate /etc/issue out of a init script.  It doesn't look like they do
>> that anymore, so perhaps we should reconsider these too
>>
>>> All the above mentioned files are configuration files by all means. Not
>>> that it's an urgent matter, but according to what you just said, then
>>> etc_runtime_t is possibly misplaced there...
> 
> Yes, some distributions generate very generic banners with the name of
> the distribution and the version. But they are just meant to be examples
> (similarly to generic configuration files installed by default in /etc
> by most packages).
> 
> They are static, so etc_t is what we need here.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2011-03-02 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 15:52 [refpolicy] [patch 1/3] Implementation of system conf type Miroslav Grepl
2011-02-19  9:57 ` Sven Vermeulen
2011-02-20  5:37   ` Guido Trentalancia
2011-02-21 15:40     ` Daniel J Walsh
2011-02-21 20:11       ` Guido Trentalancia
2011-02-22 15:46         ` Christopher J. PeBenito
2011-02-22 15:57           ` Daniel J Walsh
2011-02-22 17:27             ` Miroslav Grepl
2011-02-22 16:18           ` Guido Trentalancia
2011-03-01 19:57             ` Christopher J. PeBenito
2011-03-01 20:41               ` Guido Trentalancia
2011-03-02 14:33                 ` Christopher J. PeBenito [this message]
2011-03-02 19:10                   ` Daniel J Walsh
2011-03-03 14:36                   ` Guido Trentalancia
2011-03-03 15:32                     ` Daniel J Walsh
2011-03-04 14:21                     ` Christopher J. PeBenito
2011-03-04 19:01                       ` Guido Trentalancia
2011-03-18 22:53                       ` [refpolicy] mtab lock files label (was [patch 1/3] Implementation of system conf type) Guido Trentalancia
2011-02-22 16:27           ` [refpolicy] [patch 1/3] Implementation of system conf type Guido Trentalancia
2011-03-01 20:01             ` Christopher J. PeBenito
2011-03-01 20:32               ` Guido Trentalancia

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=4D6E5523.7040001@tresys.com \
    --to=cpebenito@tresys.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.