From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix nis_getnames
Date: Tue, 05 Dec 2006 19:52:00 -0000 [thread overview]
Message-ID: <20061205195208.GI9556@sunsite.mff.cuni.cz> (raw)
Hi!
NIS_PATH is already in UNSECURE_ENVVARS, so ld.so unsetenv's
it during start of suid/sgid programs, so all this __secure_getenv
does is prohibit suid/sgid programs to setenv NIS_PATH to some value
and expect nis_lookup or nis_list with EXPAND_NAME flag set to use it.
2006-12-05 Jakub Jelinek <jakub@redhat.com>
* nis/nis_subr.c (nis_getnames): Revert last change.
--- libc/nis/nis_subr.c.jj 2006-10-19 17:26:39.000000000 +0200
+++ libc/nis/nis_subr.c 2006-12-05 20:47:11.000000000 +0100
@@ -178,7 +178,7 @@ nis_getnames (const_nis_name name)
}
/* Get the search path, where we have to search "name" */
- path = __secure_getenv ("NIS_PATH");
+ path = getenv ("NIS_PATH");
if (path == NULL)
path = strdupa ("$");
else
Jakub
next reply other threads:[~2006-12-05 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 19:52 Jakub Jelinek [this message]
2006-12-05 21:27 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061205195208.GI9556@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).