From: hjl@valinux.com (H.J. Lu)
To: geoffk@ozemail.com.au (Geoff Keating)
Cc: libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: Re: A patch for libresolv
Date: Mon, 11 Oct 1999 17:56:00 -0000 [thread overview]
Message-ID: <19991012005611.C92F03FC1@valinux.com> (raw)
In-Reply-To: <199910120036.KAA00744@gluttony.geoffk.wattle.id.au>
>
> > Date: Mon, 11 Oct 1999 17:26:42 -0700 (PDT)
> > Cc: libc-hacker@sourceware.cygnus.com (GNU C Library)
> > From: hjl@valinux.com (H.J. Lu)
>
> > They are off by default. You have to turn them on by hand in
> > /etc/resolv.conf or via an environment variable. They are a few
> > sites on the Internet which rerquires them. I'd like to be able
> > to do
> >
> > # RES_OPTS=insecure2 foobar
> >
> > What is the problem with that? Are you suggesting we should check
> >
> > # rm -rf /dev
> >
> > now?
>
> So your proposed patch checks for getuid() == 0?
>
RES_OPTIONS is called with __secure_getenv so that it is not a problem.
However, all those options, including RES_IGNTC, are set/cleared in
dig/host/nslookup in bind 8. Right now my patch will only affect root
if those options are turned on in /etc/resolv.conf. If anyone can
change /etc/resolv.conf on your machine, my patch is the last thing
you want to worry about.
--
H.J. Lu (hjl@gnu.org)
prev parent reply other threads:[~1999-10-11 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 18:27 H.J. Lu
1999-10-11 14:47 ` Ulrich Drepper
1999-10-11 15:00 ` H.J. Lu
1999-10-11 15:07 ` Ulrich Drepper
1999-10-11 15:11 ` H.J. Lu
1999-10-11 17:20 ` Geoff Keating
1999-10-11 17:26 ` H.J. Lu
1999-10-11 17:37 ` Geoff Keating
1999-10-11 17:56 ` H.J. Lu [this message]
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=19991012005611.C92F03FC1@valinux.com \
--to=hjl@valinux.com \
--cc=geoffk@ozemail.com.au \
--cc=libc-hacker@sourceware.cygnus.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).