All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Steve G <linux_4ever@yahoo.com>,
	Daniel J Walsh <dwalsh@redhat.com>,
	SE Linux <selinux@tycho.nsa.gov>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>
Subject: Re: libselinux patch
Date: Tue, 27 Feb 2007 10:58:39 -0500	[thread overview]
Message-ID: <1172591919.11157.1.camel@sgc> (raw)
In-Reply-To: <1172589336.19041.344.camel@moss-spartans.epoch.ncsc.mil>

On Tue, 2007-02-27 at 10:15 -0500, Stephen Smalley wrote:
> On Mon, 2007-02-26 at 08:40 -0800, Steve G wrote:
> > OK, I think the attached patch does _everything _ we discussed. It:
> >  
> >  - removes 8 syscalls for the normal path
> >  - ensures /selinux is trully an selinuxfs
> >  - drops back to detecting the old way when /selinux is missing
> >  - changes the old way in is_enabled to use fopen & getline for glibc internal
> > retries
> >  - adds retry for EINTR in mls_enabled
> >  - keeps SELINUX_MAGIC private
> >  
> >  Signed-off-by: Steve Grubb <linux_4ever@yahoo.com>
> 
> Thanks, applied the revised (with fsetlocking calls) patch on the trunk,
> libselinux 2.0.5.  Note to Chris/Dan:  "allow $1 security_t:filesystem
> getattr;" should be added to selinux_get_fs_mount() in the policy to
> allow the statfs() call introduced by this patch; it won't break
> anything if it is missing (since it falls back to the old logic upon
> failure), but it should be allowed.

Added to refpolicy trunk, rev 2198.

-- 
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:[~2007-02-27 15:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 14:31 libselinux patch Daniel J Walsh
2007-02-20 15:05 ` Steve G
2007-02-20 15:06   ` Stephen Smalley
2007-02-21 13:12     ` Steve G
2007-02-21 13:20       ` Stephen Smalley
2007-02-21 13:37         ` Steve G
2007-02-21 13:42           ` Stephen Smalley
2007-02-21 14:03             ` Steve G
2007-02-21 18:26               ` Steve G
2007-02-22 12:34                 ` Stephen Smalley
2007-02-22 13:46                   ` Steve G
2007-02-22 14:10                     ` Stephen Smalley
2007-02-22 15:48                       ` Steve G
2007-02-23 20:45                         ` Stephen Smalley
2007-02-26 16:40                           ` Steve G
2007-02-27 15:15                             ` Stephen Smalley
2007-02-27 15:58                               ` Christopher J. PeBenito [this message]
2007-02-22 14:45                     ` James Antill
2007-02-21 14:47           ` Stefanos Harhalakis
2007-02-21 17:21 ` Stephen Smalley
2007-04-05 17:25 Daniel J Walsh
2007-04-05 17:44 ` Stephen Smalley
2007-04-05 21:00   ` Daniel J Walsh
2007-04-09 14:17     ` Stephen Smalley
2007-04-09 15:12       ` 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=1172591919.11157.1.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=linux_4ever@yahoo.com \
    --cc=sds@tycho.nsa.gov \
    --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.