All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Michael C Thompson <thompsmc@us.ibm.com>,
	SE Linux <selinux@tycho.nsa.gov>
Subject: Re: setsebool
Date: Thu, 13 Jul 2006 08:06:32 -0400	[thread overview]
Message-ID: <1152792392.2561.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200607130734.35344.sgrubb@redhat.com>

On Thu, 2006-07-13 at 07:34 -0400, Steve Grubb wrote:
> On Thursday 13 July 2006 06:54, Daniel J Walsh wrote:
> > Is this a problem in the Kernel or libraries?  Or just the way it is?
> 
> I think the granted statement comes from policy. I was thinking that audit of 
> granting when changing booleans would be dropped from policy when the 2.6.17 
> kernel was out.
> 

The kernel also generates a message with all of the boolean states in
addition to the auditallow. When wrote that my thought was that there
would not be that many booleans and printing them all would make it
easier to see the state of the system in the logs. Obviously I was wrong
about the number of booleans.

The message is printed from security_set_bools in services.c. Should
this just go in favor of an audit message or be changed to just print
the state of the changed booleans?

Karl

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

--
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-07-13 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44AD708E.10205@us.ibm.com>
     [not found] ` <200607061639.55819.sgrubb@redhat.com>
     [not found]   ` <44AD7553.3050605@us.ibm.com>
     [not found]     ` <200607061712.05688.sgrubb@redhat.com>
     [not found]       ` <44AE7C4E.2070500@us.ibm.com>
     [not found]         ` <44AFC876.8050501@redhat.com>
     [not found]           ` <44B54FDC.7040505@us.ibm.com>
     [not found]             ` <44B55404.6090702@redhat.com>
     [not found]               ` <44B55CB2.8010409@us.ibm.com>
     [not found]                 ` <44B560CD.7080202@redhat.com>
     [not found]                   ` <44B5623C.8060600@us.ibm.com>
2006-07-13 10:54                     ` setsebool Daniel J Walsh
2006-07-13 11:34                       ` setsebool Steve Grubb
2006-07-13 12:06                         ` Karl MacMillan [this message]
2006-07-13 12:26                           ` setsebool Stephen Smalley
2006-07-13 12:41                             ` setsebool Karl MacMillan
2006-07-13 12:58                               ` setsebool Stephen Smalley
2006-07-13 12:07                       ` setsebool Stephen Smalley
2006-07-13 12:25                         ` setsebool Steve Grubb
2006-07-13 13:37                         ` setsebool Christopher J. PeBenito

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=1152792392.2561.4.camel@localhost.localdomain \
    --to=kmacmillan@mentalrootkit.com \
    --cc=dwalsh@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=sgrubb@redhat.com \
    --cc=thompsmc@us.ibm.com \
    /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.