From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: libselinux rpm_execon should not fail in permissive mode.
Date: Mon, 24 Jan 2005 15:59:31 -0500 [thread overview]
Message-ID: <41F561B3.5090907@redhat.com> (raw)
In-Reply-To: <1106599610.19246.255.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Mon, 2005-01-24 at 15:43, Daniel J Walsh wrote:
>
>
>>diff --exclude-from=exclude -N -u -r nsalibselinux/src/rpm.c libselinux-1.21.1/src/rpm.c
>>--- nsalibselinux/src/rpm.c 2004-11-09 09:13:54.000000000 -0500
>>+++ libselinux-1.21.1/src/rpm.c 2005-01-24 15:24:33.000000000 -0500
>>@@ -41,8 +41,10 @@
>> rc = setexeccon(newcon);
>> if (rc < 0)
>> goto out;
>>- rc = execve(filename, argv, envp);
>> out:
>>+ if ( ( rc == 0 ) ||
>>+ (security_getenforce() == 0 ))
>>+ rc = execve(filename, argv, envp);
>> context_free(con);
>> freecon(newcon);
>> freecon(fcon);
>>
>>
>
>What failure are you encountering in permissive mode? Possibly the file
>might lack a context and we should handle that more cleanly, but I
>wouldn't recommend this patch. The setexeccon() shouldn't fail in
>permissive mode.
>
>
>
Basically running rpm --root
Bugzilla %145770
--
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:[~2005-01-24 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 22:48 Man pages added to policy file Daniel J Walsh
2005-01-24 20:02 ` James Carter
2005-01-24 20:43 ` libselinux rpm_execon should not fail in permissive mode Daniel J Walsh
2005-01-24 20:46 ` Stephen Smalley
2005-01-24 20:59 ` Daniel J Walsh [this message]
2005-01-24 21:01 ` Stephen Smalley
2005-01-26 13:32 ` 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=41F561B3.5090907@redhat.com \
--to=dwalsh@redhat.com \
--cc=sds@epoch.ncsc.mil \
--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.