linux-kernel - Re: Friendlier EPERM e-mail on lkml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20130109173304.GA16391@cachalot>
Date:	Wed, 9 Jan 2013 21:33:04 +0400
From:	Vasily Kulikov <segoon@...nwall.com>
To:	Eric Paris <eparis@...isplace.org>
Cc:	LSM List <linux-security-module@...r.kernel.org>,
	linux-kernel@...r.kernel.org, libc-alpha@...rceware.org
Subject: Re: Friendlier EPERM e-mail on lkml

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/