Messages in this thread | | | Date | Mon, 06 Oct 2008 17:08:27 -0700 | From | Ulrich Drepper <> | Subject | Re: [PATCH] ELF: implement AT_RANDOM for future glibc use |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Roland McGrath wrote: > What glibc wants is some bits with a strength of randomness chosen by the > kernel, and not to worry about the details. I think the strength applied > to mmap and stack randomization is good enough for AT_RANDOM.
I think the decision about the pool should be hidden behind some interface. I agree, the AT_RANDOM data and ASLR can live with the same type of data.
But perhaps we can make the interface a bid more complex for SUID and uid==0 binaries.
Also, for platforms with cheap random data sources (VIA Padlock, hopefully more in future).
- -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkjqqHsACgkQ2ijCOnn/RHRRVgCeIQDpaol6HXgTdzpGcQKn40lp ZX4An1HBITlkN/hRHe1Cqy8/QUuZ7ZyX =nQuu -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |