[Patch] Document __secure_getenv

Florian Weimer fweimer@redhat.com
Thu Jul 12 13:42:00 GMT 2012


On 07/11/2012 06:06 PM, Carlos O'Donell wrote:
> On 7/11/2012 11:44 AM, Florian Weimer wrote:
>> I cannot use the new symbol because that would introduce a dependency on a new libc version.
>
> Use <new name for __secure_getenv> if libc supports it,
> otherwise keep using __secure_getenv.
>
> After adding the new interface we can make __secure_getenv
> hidden so no new programs can't be linked against it.

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.

-- 
Florian Weimer / Red Hat Product Security Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: secure_getenv.patch
Type: text/x-patch
Size: 1727 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20120712/965760fe/attachment.bin>


More information about the Libc-alpha mailing list