From: Vasily Kulikov <segoon@openwall.com>
To: Eric Paris <eparis@parisplace.org>
Cc: LSM List <linux-security-module@vger.kernel.org>,
linux-kernel@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: Friendlier EPERM e-mail on lkml
Date: Wed, 9 Jan 2013 21:33:04 +0400 [thread overview]
Message-ID: <20130109173304.GA16391@cachalot> (raw)
In-Reply-To: <CACLa4pvNYRLGG2t9Y40BYbqnxu9oTYjMWs71C9soJEiwzBMK5Q@mail.gmail.com>
Hi Eric,
On Wed, Jan 09, 2013 at 11:18 -0500, Eric Paris wrote:
> http://marc.info/?l=linux-kernel&m=135774748910987&w=2
>
> Basic idea is a proc file which tells you WHY the last EPERM from the
> kernel happened. Was it SELinux? Was it SMACK? Was it capabilities?
> Was it file rwx bits?
>
> I'd like comments. I'll cc LSM on any future replies to that thread...
Why does application need it? Why does anybody but admin need this
information?
Probably this may be implemented as root-only audit messages? Or
introduce new NETLINK_EPERMREASON netlink family?
--
Vasily Kulikov
http://www.openwall.com - bringing security into open computing environments
parent reply other threads:[~2013-01-09 17:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CACLa4pvNYRLGG2t9Y40BYbqnxu9oTYjMWs71C9soJEiwzBMK5Q@mail.gmail.com>]
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=20130109173304.GA16391@cachalot \
--to=segoon@openwall.com \
--cc=eparis@parisplace.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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