🚀 go-pugleaf

Charles William Swiger <cs4w+@andrew.cmu.edu> writes:

>If you're on a network, don't make /dev/kmem world readable or
>writable...that definitely is a security hole.

Or even if you're not on a network, but others may be logging into
your machine (via dialup or whatever).
If someone can read /dev/kmem, they can basically find out
everything that is going on with every program. 
If they can write /dev/kmem, ... well, you might as well give them
the root password. :-)

It's probably not a terrific idea, but one way around this fixing
permissions is to put yourself into group kmem.  That way, you can
read/write /dev/kmem, but others still cannot.  The only 'risk' here
is to make sure that you don't accidentally modify /dev/kmem by
writing to it.  You are not likely to do this unless you really
try. 
-- 
David Lemson                                                (217) 244-1205
University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin
Internet : lemson@uiuc.edu                UUCP :...!uiucuxc!uiucux1!lemson 
NeXTMail accepted                                  BITNET : LEMSON@UIUCVMD