Re: euidaccess

[Jim Meyering]

Bruno Haible wrote:
> Jim Meyering wrote:
>> For some of the same reasons, the euidaccess function/module should be
>> avoided, simply because it cannot be used robustly -- by its very nature.
>> Use faccessat instead.
>
> Here's a proposed doc update and additional warnings for the use of
> 'access' and 'euidaccess' (guarded by GNULIB_POSIXCHECK):
>
> 2010-03-06  Bruno Haible  <address@hidden>
>
>       Clarify access, euidaccess, faccessat.
>       * doc/posix-functions/faccessat.texi: Mention security problem under
>       "Other problems", not "Portability problems".
>       * doc/posix-functions/access.texi: Likewise. Mention a related security
>       problem.
>       * doc/glibc-functions/euidaccess.texi: Mention security problems.
>       * lib/euidaccess.c: Add comments about platforms.
>       * lib/unistd.in.h (access, euidaccess): Add warnings.

Thanks for the comments and documentation improvements.
They all look fine.