[1139] in bugtraq
Re[2]: snooper watchers
daemon@ATHENA.MIT.EDU (Nayfield, Rod)
Wed Mar 1 11:39:35 1995
Date: Wed, 01 Mar 95 08:37:22 EST
From: "Nayfield, Rod" <rnayfield@mail.iconnet.com>
To: proff@suburbia.apana.org.au, Karl Strickland <karl@bagpuss.demon.co.uk>
Cc: jna@concorde.com, bugtraq@fc.net
The best thing to do is take the nit support out of the kernel and
remove /dev/nit. Now someone would have to build a new kernel and
reboot the machine to replace the nit support.
If you are overly concerned about this, you can set the boot device
(in the rom monitor on a sparc) to boot off of some other disk, one
that is not bootable or not there. Then a reboot/fastboot/shutdown
-r/etc will not be able to automatically bring the system up. I don't
believe that you can specify boot devices from a unix reboot type
command.
Of course this means you have to go to the console each time you want
to boot, and you won't get reboots on failures/etc.
rod
______________________________ Reply Separator _________________________________
Subject: Re: snooper watchers
Author: Karl Strickland <karl@bagpuss.demon.co.uk> at Internet
Date: 2/28/95 10:50 PM
whats this mean
is someone saying rm'ing /dev/nit and hacking mknod out of the kernel is better
than just taking nit out of the kernel?
