| 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
| ||
|
Message-ID: <20081004164239.0c1483a4@infradead.org> Date: Sat, 4 Oct 2008 16:42:39 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Kees Cook <kees.cook@...onical.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] proc: add "personality" to process status file On Sat, 4 Oct 2008 15:02:20 -0700 Kees Cook <kees.cook@...onical.com> wrote: > On Sat, Oct 04, 2008 at 02:51:49PM -0700, Arjan van de Ven wrote: > > On Thu, 2 Oct 2008 14:14:24 -0700 > > Kees Cook <kees.cook@...onical.com> wrote: > > > > > There is no sane way to query the personality flags of arbitrary > > > process from userspace. This adds the flags to > > > the /proc/$pid/status file. For example, to detect > > > READ_IMPLIES_EXEC: > > > > > > > .. I'm sure local exploit writers will love this to find out which > > processes to attack. > > Realistically, this probably shouldn't be in a world-readable file. > > Nothing else seemed appropriate, but I could make a brand new proc > file, if that's sensible. "status_private" ? how about a file called "personality" that has each set bit as an ascii version ? (one per line maybe) -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/
Powered by blists - more mailing lists