From: Stephen Smalley <sds@tycho.nsa.gov>
To: Jay Corrales <jscorrales1122@gmail.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: /bin/bash: Bad interpreter: Permission denied.
Date: Wed, 18 Dec 2013 17:02:50 -0500 [thread overview]
Message-ID: <52B21B8A.2030108@tycho.nsa.gov> (raw)
In-Reply-To: <CACVacMssmARBBZEp_2GEnnKORu2tfdJMzMC2LjMZ8CuEcpKZEw@mail.gmail.com>
On 12/18/2013 04:53 PM, Jay Corrales wrote:
> On 12/18/13, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>> On 12/18/2013 10:32 AM, Jay Corrales wrote:
>>> Folks,
>>>
>>> We think we've run into a bug with rhel5. Could be that the policy
>>> database contains corruption, or contains some data structures that lead
>>> to buggy results (e.g. AVC execute_no_trans). Is there a way to see
>>> additional debug info in the LSM during run time? I've tried adding
>>> "debug" to the boot time kernel parameters, but does not add any new
>>> logging or reporting info for selinux.
>>
>> More likely just a bug in your policy. I can't really tell though as
>> you haven't shown an AVC that corresponds to the policy that you listed.
>
> We restored an image of our previous build and ran the policy. There
> was no perm denied error. It ran perfectly. The difference in builds
> represents an installer media and updated policies. leading me to
> believe there is something fundamentally wrong with the installer
> media producing a corrupted policy database.
>
> Is there a way to know why it is reporting an AVC for
> execute_no_trans? The audit.log does not show enough info for this. We
> were hoping for some way to look at the LSM, other than running an
> embedded kernel and attaching gdb.
nosuid mount would suppress the transition.
Or maybe you don't have the type_transition rule in your policy at all?
next prev parent reply other threads:[~2013-12-18 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 16:23 /bin/bash: Bad interpreter: Permission denied Jay Corrales
2013-12-17 16:35 ` Stephen Smalley
2013-12-17 18:03 ` Jay Corrales
2013-12-17 18:15 ` Stephen Smalley
[not found] ` <CACVacMu4EvcdZzLVbBRFUvgg_RA0Mc7awZ0x_mzoxadmO6TSkw@mail.gmail.com>
2013-12-18 15:32 ` Jay Corrales
2013-12-18 17:55 ` Stephen Smalley
2013-12-18 21:53 ` Jay Corrales
2013-12-18 22:02 ` Stephen Smalley [this message]
2013-12-19 4:39 ` Jay Corrales
2013-12-18 20:14 ` Stephen Smalley
2013-12-18 21:46 ` Jay Corrales
2013-12-18 21:52 ` Stephen Smalley
2013-12-18 21:55 ` Jay Corrales
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=52B21B8A.2030108@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=SELinux@tycho.nsa.gov \
--cc=jscorrales1122@gmail.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.