All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: libselinux patch
Date: Mon, 09 Apr 2007 11:12:23 -0400	[thread overview]
Message-ID: <461A57D7.3040704@redhat.com> (raw)
In-Reply-To: <1176128256.15415.71.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2007-04-05 at 17:00 -0400, Daniel J Walsh wrote:
>   
>> Second pass.
>>
>>
>> plain text document attachment (diff)
>>     
>
>   
>> diff --exclude-from=exclude -N -u -r nsalibselinux/utils/getsebool.c libselinux-2.0.9/utils/getsebool.c
>> --- nsalibselinux/utils/getsebool.c	2006-11-16 17:15:17.000000000 -0500
>> +++ libselinux-2.0.9/utils/getsebool.c	2007-04-05 16:57:51.000000000 -0400
>> @@ -14,7 +14,7 @@
>>  
>>  int main(int argc, char **argv)
>>  {
>> -	int i, rc = 0, active, pending, len = 0, opt;
>> +	int i, get_all = 0, rc = 0, active, pending, len = 0, opt;
>>  	char **names;
>>  
>>  	while ((opt = getopt(argc, argv, "a")) > 0) {
>> @@ -39,6 +39,7 @@
>>  				printf("No booleans\n");
>>  				return 0;
>>  			}
>> +			get_all = 1;
>>  			break;
>>  		default:
>>  			usage(argv[0]);
>> @@ -72,6 +73,8 @@
>>  	for (i = 0; i < len; i++) {
>>  		active = security_get_boolean_active(names[i]);
>>  		if (active < 0) {
>> +			if (! get_all && errno == EACCES) 
>> +				continue;
>>     
>
> Shouldn't that be if (get_all && errno == EACCES)?
> The goal is to only suppress the warnings upon getsebool -a, not the
> other way around.
>
>   
Yes. 
>>  			fprintf(stderr, "Error getting active value for %s\n",
>>  				names[i]);
>>  			rc = -1;
>>     


--
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-04-09 15:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 17:25 libselinux patch 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-20 14:31 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
2007-02-22 14:45                     ` James Antill
2007-02-21 14:47           ` Stefanos Harhalakis
2007-02-21 17:21 ` 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=461A57D7.3040704@redhat.com \
    --to=dwalsh@redhat.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.