Path: utzoo!utgpu!attcan!uunet!steinmetz!vdsvax!montnaro
From: montnaro@sprite.steinmetz.ge.com (Skip Montanaro)
Newsgroups: comp.windows.news
Subject: Re: remote NeWS servers
Message-ID: <MONTNARO.88Oct10121454@sprite.steinmetz.ge.com>
Date: 10 Oct 88 16:13:06 GMT
References: <8809292102.AA10538@cleo.sw.mcc.com>
Sender: news@vdsvax.steinmetz.ge.com
Reply-To: <montanaro@sprite.steinmetz.ge.com> (Skip Montanaro)
Organization: GE Corporate Research & Development
Lines: 28
In-reply-to: peterson@SW.MCC.COM's message of 5 Oct 88 03:24:41 GMT

James Peterson writes:
   Rich Berlin writes:
   > ... To make machine yyyy a trusted
   > host, you must execute the command
   > 
   > newshost add yyyy
   >
   > on machine xxxx.

   Another possibility is to modify the value of NetSecurityWanted in 
   lib/NeWS/init.ps:

   /NetSecurityWanted false def	% false if everyone is allowed to connect

Ay, Ay, Ay! Don't do this in /usr/NeWS/lib/NeWS/init.ps!!! You should not
make the assumption that all users that access /usr/NeWS (possibly via NFS)
want what little security exists to be disabled. Have the user execute the
above line from his/her ~/user.ps

Better yet, users should leave NetSecurityWanted true, then enable specific
machines to communicate via lines like:

   RemoteHostRegistry /moose true put

which allows client programs on "moose" to connect to my machine's server.

--
Skip Montanaro (montanaro@sprite.steinmetz.ge.com, montanaro@ge-crd.arpa)