[patch] res_conf.h missing security feature

Ben Collins bcollins@debian.org
Mon Jan 8 09:55:00 GMT 2001


On Mon, Jan 08, 2001 at 09:48:10AM -0800, Ulrich Drepper wrote:
> Ben Collins <bcollins@debian.org> writes:
> 
> > Seems this fix didn't make it throught the resolv migration in glibc 2.2
> 
> Nope, this is wrong.  There was a comma missing in a different file.
> Check the CVS archive.

Yeah, I got the email from Jakub. I wasn't aware that __secure_getenv
was dropped in favor of the new machanism. Is the header listing
supposed to obsolete the __secure_getenv calls? Or is the header listing
used for the most touched parts of the code, and __secure_getenv saved
for obscure cases that don't get called much?

The reason I ask is that it wasn't very apparent since res_query.c still
used __secure_getenv for one env, while the rest of the resolv code
dropped that usage in favor the secure env header. Just looking for some
consistency.

Ben

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'


More information about the Libc-alpha mailing list