From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>,
Karl MacMillan <kmacmillan@mentalrootkit.com>,
Joshua Brindle <jbrindle@tresys.com>
Subject: Re: Minor change to getsebool.
Date: Thu, 08 Mar 2007 11:28:04 -0500 [thread overview]
Message-ID: <45F03994.7060504@redhat.com> (raw)
In-Reply-To: <1173370754.10467.86.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2007-03-08 at 11:12 -0500, Daniel J Walsh wrote:
>
>> Should be non fatail when executing getsebool -a. I am starting to
>> label the booleans and
>> different user roles will only be able to manipulate certain booleans.
>>
>> So we need to change
>>
>> getsebool -a will only show booleans that domain can manipulate.
>> Currenly it will report the errrors that it can not read. We can either
>> add a qualifier to silence these or a new option to get only the list of
>> the ones I can manipulate.
>>
>
> Actually, I'd tend to think we could just silence them by default if
> errno is EACCES.
>
> One other possible change to getsebool would be to make it fully
> equivalent to setsebool, i.e. add a -P option and have it query
> libsemanage to get persistent boolean settings in that case.
>
>
Then it needs to move from libselinux to policycoreutils.
--
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.
next prev parent reply other threads:[~2007-03-08 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:12 Minor change to getsebool Daniel J Walsh
2007-03-08 16:19 ` Stephen Smalley
2007-03-08 16:28 ` Daniel J Walsh [this message]
2007-03-08 16:29 ` Stephen Smalley
2007-03-09 7:42 ` Russell Coker
2007-03-08 19:47 ` Christopher J. PeBenito
2007-03-08 20: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=45F03994.7060504@redhat.com \
--to=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=kmacmillan@mentalrootkit.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.