🚀 go-pugleaf

In article <Bv6yB1.5r5@ux1.cso.uiuc.edu> lemson@ux1.cso.uiuc.edu (David Lemson) writes:
>gad@eclipse.its.rpi.edu (Garance A. Drosehn) writes:
>
>>jgg@proforma.com (J. G. Gregory) writes:
>>>    Under "Security Options" turn on "Public Window Server".  This is a
>>>    security weakness, and I don't understand how severe.  However, I am
>To further emphasize why this is a hazard - when you have Public
>Window Server turned on, anyone who has an internet connection to your
>machine can perform tasks on your machine with the same security
>equivalence as the person who is currently logged into the console
>of the machine. (without a whole lot of trouble)

If u read the online documentation about security, NeXT has added an option
into the NetInfo to disable Public Window Server, and Public Sound.  So
everyone who has account on the NeXT won't have Public Window & Sound
Server turned on.  look at /NextLibrary/Documentation/NextAdmin/14_Security/
01_Implementing.rtfd
-- 
Mul			    |  Alt. address: sulistio@futon.sfsu.edu
sulistio@sutro.sfsu.edu     |		     sulistio@sfsuvax1.sfsu.edu
#include "std/disclaimer.h" |		     mul@wet.UUCP  (UUCP e-mail)
	NeXT-Mail accepted at:  sarong!sulistio@cs.sfsu.edu (UUCP e-mail)