All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Orr <martin@martinorr.name>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: "Václav Ovsík" <vaclav.ovsik@i.cz>, selinux@tycho.nsa.gov
Subject: Re: refpolicy HEAD, Debian, patch for udev.te
Date: Tue, 04 Dec 2007 10:41:19 +0000	[thread overview]
Message-ID: <47552ECF.4020105@martinorr.name> (raw)
In-Reply-To: <1196551302.4808.6.camel@defiant.pebenito.net>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On 01/12/07 23:21, Chris PeBenito wrote:
> On Fri, 2007-11-30 at 17:24 +0000, Martin Orr wrote:
>> On 30/11/07 15:55, Christopher J. PeBenito wrote:
>>> On Fri, 2007-11-30 at 16:30 +0100, Václav Ovsík wrote:
>>>> On Fri, Nov 30, 2007 at 09:38:33AM -0500, Christopher J. PeBenito wrote:
>>>>>> Corresponding code is in udev_node.c, function node_symlink().
>>>>>>     if (strcmp(target, buf) == 0) {
>>>>>> 	    info("preserve already existing symlink '%s' to '%s'", slink,
>>>>>> target);
>>>>>> 	    selinux_setfilecon(slink, NULL, S_IFLNK);
>>>>>> 	    goto exit;
>>>>>>     }
>>>>> I'll add the rule.  Perhaps someone should send up a patch to remove the
>>>>> setfilecon, and update the info message.
> Yes, thats what I was thinkin.  Since the function is node_symlink(),
> I'm guessing there is a similar function for char and block node, etc?
> Those should be checked to make sure they don't do unneeded relabeling
> too.

That's true.  And for char and block nodes, it also does a chmod to reset
the permissions.  Apparently this is intended, because "you can't expect
that the properties of a pre-existing node are correct."

Best wishes,

-- 
Martin Orr


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-12-04 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 14:45 refpolicy HEAD, Debian, patch for udev.te Václav Ovsík
2007-11-27 18:49 ` Christopher J. PeBenito
2007-11-29 20:06   ` Martin Orr
2007-11-30 13:49     ` Václav Ovsík
2007-11-30 14:38       ` Christopher J. PeBenito
2007-11-30 15:30         ` Václav Ovsík
2007-11-30 15:55           ` Christopher J. PeBenito
2007-11-30 17:24             ` Martin Orr
2007-12-01 23:21               ` Chris PeBenito
2007-12-04 10:41                 ` Martin Orr [this message]
2007-12-04 14:07                 ` Daniel J Walsh

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=47552ECF.4020105@martinorr.name \
    --to=martin@martinorr.name \
    --cc=pebenito@gentoo.org \
    --cc=selinux@tycho.nsa.gov \
    --cc=vaclav.ovsik@i.cz \
    /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.