|author||Rich Felker <email@example.com>||2014-07-17 22:01:52 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2014-07-17 22:01:52 -0400|
provide getauxval(AT_SECURE) even if it is missing from the aux vector
this could happen on 2.4-series linux kernels that predate AT_SECURE and possibly on other kernels that are emulating the linux syscall API but not providing AT_SECURE in the aux vector at startup. in principle applications should be checking errno anyway, but this does not really work. to be secure, the caller would have to treat ENOENT (indeterminate result) as possibly-suid and thereby disable functionality in the typical non-suid usage case. and since glibc only runs on kernels that provide AT_SECURE, applications written to the glibc getauxval API might simply assume it succeeds.
Diffstat (limited to 'arch/powerpc')
0 files changed, 0 insertions, 0 deletions