From: Bill Tangren <bjt@usno.navy.mil>
Cc: linux-audit@redhat.com
Subject: Re: "denied" error message
Date: Wed, 25 Jul 2007 16:03:23 -0400 [thread overview]
Message-ID: <46A7AC8B.7020506@usno.navy.mil> (raw)
In-Reply-To: <46A79EB5.7050206@usno.navy.mil>
Bill Tangren wrote:
> I have the following error message showing up in my audit logs. This is
> on an SELinux-enabled web server (running RHEL ES 4, fully patched).
> This is actually an selinux error, so if this not the correct place to
> ask this question, please let me know.
>
Never mind. I got at least a partial answer by googling NSA's selinux mailing
list archive. I quote from one of those pages:
"Typically, that audit message suggests that kernel is translating PROT_READ
requests by that binary to PROT_READ|PROT_EXECUTE in order to provide
compatibility with "legacy" binaries that presumed read-implies-exec logic."
This is an old program that is calling shared libraries. It isn't hurting the
program, but it is filling up my audit logs. I guess I'll leave it alone.
Thanks anyway.
next prev parent reply other threads:[~2007-07-25 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 19:04 "denied" error message Bill Tangren
2007-07-25 20:03 ` Bill Tangren [this message]
2007-07-26 12:36 ` 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=46A7AC8B.7020506@usno.navy.mil \
--to=bjt@usno.navy.mil \
--cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox