Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!SW.MCC.COM!peterson
From: peterson@SW.MCC.COM (James Peterson)
Newsgroups: comp.windows.news
Subject: Re: remote NeWS servers
Message-ID: <8809292102.AA10538@cleo.sw.mcc.com>
Date: 5 Oct 88 03:24:41 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 31

Rich Berlin writes:
> > In article <643@prlhp1.prl.philips.co.uk> Richard Cole writes:
> > 
> > I get the following message on the server
> > 
> >   Network security violation:
> >   Rejected connection from yyyy
> > 
> > where yyyy is the id of the mechine originating the message.
> 
> ... 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

By default this variable is shipped as true.  If it is true, then
network security is used, as Rich described.  When it is false, the
entire process is ignored and any machine can access any other --
much easier in a trusted environment.  (In theory, if NetSecurityWanted
is false, an undergraduate with access to the Internet at Berkeley
could pop windows up on a screen at Maryland, so you have to consider
ALL machines that can access yours).

jim