linux-kernel - Re: [PATCH] proc: add "personality" to process status file

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20081005004233.GL10632@outflux.net>
Date:	Sat, 4 Oct 2008 17:42:33 -0700
From:	Kees Cook <kees.cook@...onical.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] proc: add "personality" to process status file

On Sat, Oct 04, 2008 at 04:42:39PM -0700, Arjan van de Ven wrote:
> On Sat, 4 Oct 2008 15:02:20 -0700
> Kees Cook <kees.cook@...onical.com> wrote:
> > 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)

Well, it's a one-to-many due to how the personality types are defined,
so doing a bitfield-to-ASCII-names conversion wouldn't really work out:

        PER_SCOSVR3 =           0x0003 | STICKY_TIMEOUTS |
                                         WHOLE_SECONDS | SHORT_INODE,
        PER_OSR5 =              0x0003 | STICKY_TIMEOUTS | WHOLE_SECONDS,
...
        PER_BSD =               0x0006,
        PER_SUNOS =             0x0006 | STICKY_TIMEOUTS,

But I can certainly just make it a stand-alone file with just the
bitfield.  Or, I can still do the conversion and ignore PER_OSR5 and
PER_SUNOS.

-Kees

-- 
Kees Cook
Ubuntu Security Team
--
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/