From: Alexander Viro <aviro@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com, David Woodhouse <dwmw2@redhat.com>
Subject: Re: [PATCH] arch filter lists with < or > should not be accepted
Date: Fri, 29 Sep 2006 08:46:22 -0400 [thread overview]
Message-ID: <20060929124622.GO17710@devserv.devel.redhat.com> (raw)
In-Reply-To: <1159479981.3228.144.camel@localhost.localdomain>
On Thu, Sep 28, 2006 at 05:46:21PM -0400, Eric Paris wrote:
> Currently the kernel audit system represents arch's as numbers and will
> gladly accept comparisons between archs using >, <, >=, <= when the only
> thing that makes sense is = or !=. I'm told that the next revision of
> auditctl will do this checking but this will provide enforcement in the
> kernel even for old userspace. A simple command to show the issue would
> be to run
>
> auditctl -d entry,always -F arch>i686 -S chmod
>
> with this patch the kernel will reject this with -EINVAL
>
> Please comment/ack/nak as soon as possible.
ACK
prev parent reply other threads:[~2006-09-29 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:46 [PATCH] arch filter lists with < or > should not be accepted Eric Paris
2006-09-29 12:46 ` Alexander Viro [this message]
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=20060929124622.GO17710@devserv.devel.redhat.com \
--to=aviro@redhat.com \
--cc=dwmw2@redhat.com \
--cc=eparis@redhat.com \
--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 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.