linux-kernel - Re: [PATCH v5] ELF: implement AT

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: <20081021130111.b8d73625.akpm@linux-foundation.org>
Date:	Tue, 21 Oct 2008 13:01:11 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Kees Cook <kees.cook@...onical.com>
Cc:	drepper@...hat.com, jakub@...hat.com, arjan@...radead.org,
	roland@...hat.com, linux-kernel@...r.kernel.org,
	libc-alpha@...rceware.org
Subject: Re: [PATCH v5] ELF: implement AT_RANDOM for glibc PRNG seeding

On Fri, 3 Oct 2008 10:59:17 -0700
Kees Cook <kees.cook@...onical.com> wrote:

> While discussing[1] the need for glibc to have access to random bytes
> during program load, it seems that an earlier attempt to implement
> AT_RANDOM got stalled.  This implements a random 16 byte string, available
> to every ELF program via a new auxv AT_RANDOM vector.
> 
> [1] http://sourceware.org/ml/libc-alpha/2008-10/msg00006.html

I read the above changeloglet and read the above-linked page and it's
still 87% unclear to me what this feature does.  Something to do with
stack randomisation, apparently.  I suppose I could go do further
hunting, but from the quality-of-changelog POV I don't think I should
need to do so.

IOW: better changelog, please.

It's unclear to me that the random-number issue got sorted out?
--
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/