All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Erich Schubert <erich@debian.org>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: refpolicy updates from debian
Date: Tue, 05 Sep 2006 10:37:52 -0400	[thread overview]
Message-ID: <1157467072.3199.255.camel@sgc> (raw)
In-Reply-To: <1157466795.20129.1.camel@wintermute.xmldesign.de>

On Tue, 2006-09-05 at 16:33 +0200, Erich Schubert wrote:
> Hello Christopher,
> > this.  I have added the appropriate rules and fc entries.  However, I
> > don't see any options for usbmodules that would have it write to
> > usb.ids, so why does your patch have this access?
> 
> It's not supposed to, there is a script called update-usbids which does
> that. I assume it's being called from package postinsts, and should run
> with these permissions fine. But I havn't tested that. But usually the
> package managers can write regular files, can't they?

Yes, but what I'm referring to is:

+allow usbmodules_t usbmodules_var_lib_t:dir rw_dir_perms;
+allow usbmodules_t usbmodules_var_lib_t:file create_file_perms;

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


--
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.

  reply	other threads:[~2006-09-05 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02  1:37 refpolicy updates from debian Erich Schubert
2006-09-04 18:21 ` Christopher J. PeBenito
2006-09-04 19:43   ` Erich Schubert
2006-09-05 14:02     ` Christopher J. PeBenito
2006-09-05 14:33       ` Erich Schubert
2006-09-05 14:37         ` Christopher J. PeBenito [this message]
2006-09-05 16:19           ` Erich Schubert

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=1157467072.3199.255.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=erich@debian.org \
    --cc=selinux@tycho.nsa.gov \
    /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.