[3220] in bugtraq

home help back first fref pref prev next nref lref last post

Re: libresolv+ bug

daemon@ATHENA.MIT.EDU (David Holland)
Tue Aug 20 02:10:50 1996

Date: 	Mon, 19 Aug 1996 14:26:37 -0400
Reply-To: Bugtraq List <BUGTRAQ@NETSPACE.ORG>
From: David Holland <dholland@hcs.harvard.edu>
To: Multiple recipients of list BUGTRAQ <BUGTRAQ@NETSPACE.ORG>
In-Reply-To:  <199608190818.JAA17409@cableol.net> from "Alan Cox" at Aug 19,
              96 09:18:41 am

 > > Reading restricted file is not that much of a problem as long as you keep
 > > the contents of the files secret, i.e., don't print "root:<pw>:::": parse
 > > error at line 1.  Validate your input (for $TZ and $TERMINFO/$TERMCAP,
 > > validating input is pretty easy, $TZ and $TERM* will only reveal
 > > information if it happens to be in the right format)
 >
 > In the case of resolv, user resolv files should only be read if they are
 > accessible as that user. This means going through all the usual mess because
 > the designers of Unix didnt anticipate the fact that open(...., O_ASRUID)
 > would have been useful.

One could argue that in a setuid program such user-supplied settings
should be ignored.

--
   - David A. Holland          | Number of words in the English language that
     dholland@hcs.harvard.edu  | exist because of typos or misreadings: 381

home help back first fref pref prev next nref lref last post