All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>,
	"ivg2@cornell.edu" <"Ivan Gyurdiev"@redhat.com>
Subject: SELinux policy discussion.
Date: Wed, 15 Sep 2004 16:03:15 -0400	[thread overview]
Message-ID: <4148A003.6080309@redhat.com> (raw)

Ivan Gyurdiev (ivg2@cornell.edu) Has reported a bug that several files 
in /etc/ are world readable and yet SELinux is
preventing them from being read.  Should we add usercanread attribute to 
most of these files (/etc/exports, /etc/yp.servers) ?
Any file in /etc/ that has a security_context other than etc_t and 
doesn't have an attribute of usercanread, is a problem.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129584


Dan

--
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:[~2004-09-15 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 20:03 Daniel J Walsh [this message]
2004-09-16  0:38 ` SELinux policy discussion Colin Walters
     [not found]   ` <1095302625.28466.56.camel@localhost.localdomain>
2004-09-16  4:05     ` Colin Walters
2004-09-16  4:15       ` Colin Walters
2004-09-16 12:25         ` Daniel J Walsh
2004-09-16 13:32           ` Stephen Smalley
     [not found]       ` <1095318426.32510.30.camel@localhost.localdomain>
2004-09-16 17:37         ` Colin Walters
2004-09-16 19:53           ` Ivan Gyurdiev
2004-09-17  9:27             ` Luke Kenneth Casson Leighton
2004-09-17 17:19             ` Valdis.Kletnieks
2004-09-18 23:50               ` Dax Kelson
2004-09-24 15:24                 ` Russell Coker
2004-09-16 21:21           ` Daniel J Walsh
2004-09-16 21:46             ` Colin Walters

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=4148A003.6080309@redhat.com \
    --to=dwalsh@redhat.com \
    --cc="Ivan Gyurdiev"@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.