This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
__secure_getenv has been available basically since forever. I hope it's not going away. In application code, an alternative name would need a configure check or libc version check, plus an out-of-line copy or fallback to __secure_getenv. Perhaps this is avoidable.
The __ namespace is reserved for the implementation, unless you are part of the implementation you should not rely on anything there.
If the community wants to export __secure_getenv, then as Roland says, we should export it with a public name and document the behaviour.
Your next steps: - Work up a patch that gives __secure_getenv a public interface. - Fixup the documentation to use the new interface name.
-- Florian Weimer / Red Hat Product Security Team
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |