Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!shelby!decwrl!sgi!msc@ramoth.sgi.com From: msc@ramoth.sgi.com (Mark Callow) Newsgroups: comp.sys.sgi Subject: Re: Network Security Violations Message-ID: <33445@sgi.SGI.COM> Date: 23 May 89 19:08:23 GMT References: <8905222009.AA03121@lerc08.nas.nasa.gov> Sender: daemon@sgi.SGI.COM Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 28 In article <8905222009.AA03121@lerc08.nas.nasa.gov>, fsfacca@LERC08.NAS.NASA.GOV (Tony Facca) writes: > In Response, Mark Callow writes: > > >> The real problem here seems to be that someone edited the hosts file and > >> added loopback as the first name on the 127.1 line. The problem has nothing > ^^^^^^^^^^^^^^^^^^^^^^^ > >> to do with the upgrade to 3.1D. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > I agree that init.ps is not a file which should be modified. It should also be > pointed out however, that if you DO make all of your changes in the > /usr/NeWS/lib/user.ps file, an operating system upgrade will indeed wipe out > this file. The installation procedure does not check to see if users have > modified the system default user.ps file. This is true up to and including > the 3.1D release. > > So if you make changes to the user.ps file (which is where they should be made),be sure to copy it to somewhere safe. With this in mind, it is entirely > possible that the upgrade could cause problems of this nature. > It was the file /etc/hosts that was modified. This is certainly not overwritten on installation. Therefore I stand by my statement that the original problem was not caused by the upgrade. That user.ps is being overwritten is a bug. It will be fixed in Release 3.2. -- -Mark