Re: [Patch] Document __secure_getenv

[Florian Weimer <fweimer at redhat dot com>]

On 07/12/2012 06:48 PM, Siddhesh Poyarekar wrote:
> On Thu, 12 Jul 2012 15:42:01 +0200, Florian wrote:
> > I'm trying to do this, but I can't get __secure_getenv exported, and
> > the internal references do not use a GLIBC_PRIVATE symbol either.
> >
> > I've attached my current attempt.  (I know that I'll eventually have
> > to update the abilist files.)
> >
> > Is there a symbol which shared a similar fate?  Then I could
> > duplicate what was done back then.
>
> __secure_getenv is already exported, so I assume you mean
> secure_getenv? I assume you've already done this to strong_alias
> secure_getenv to __secure_getenv:

I don't want to use secure_getenv for the public symbol because I think 
I need three symbols: __secure_getenv (public, but without a default 
version) for backwards compatibility, getenv_secure (public) for the new 
interface, and __getenv_secure (GLIBC_PRIVATE) for the internal 
cross-references, both within libc itself and from libnss_hesiod and others.

At least that's the plan.  I still have trouble mapping this to the libc 
symbol versioning macros (which I must use so that I can get the right 
compatibility version for __secure_getenv symbol).

--
Florian Weimer / Red Hat Product Security Team