All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Antill <james.antill@redhat.com>
To: Chuck Mead <csm@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: permissions on /proc/self/attrib/current
Date: Tue, 06 Jun 2006 18:16:33 -0400	[thread overview]
Message-ID: <1149632193.13928.71.camel@code.and.org> (raw)
In-Reply-To: <4485C100.4030805@redhat.com>

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

On Tue, 2006-06-06 at 13:53 -0400, Chuck Mead wrote:

> The file /proc/self/attrib/current is world read and write. Is this
> correct? Why does it need world read and write?

 Just my opinion but...

/proc/self/attr/* are only used as part of SELinux policy, so it makes
sense for their access control to be limited by just SELinux policy.

-- 
James Antill <james.antill@redhat.com>
Red Hat

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-06-06 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 17:53 permissions on /proc/self/attrib/current Chuck Mead
2006-06-06 22:16 ` James Antill [this message]
2006-06-10  2:06   ` Russell Coker
2006-06-12 13:30 ` Stephen Smalley
2006-06-12 13:45   ` Chuck Mead
2006-06-12 14:51     ` Stephen Smalley

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=1149632193.13928.71.camel@code.and.org \
    --to=james.antill@redhat.com \
    --cc=csm@redhat.com \
    --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.