Date: Wed, 14 Aug 1996 18:03:14 -0400 From: "Kevin P. Neal" <kpneal@interpath.com> To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: jgreco@brasil.moneng.mei.com, ulf@lamb.net, jkh@time.cdrom.com, hackers@freebsd.org Subject: Re: Nightmare. Message-ID: <1.5.4.32.19960814220314.0074ba08@interpath.com>
next in thread | raw e-mail | index | archive | help
At 04:30 PM 8/14/96 -0500, Joe Greco wrote:
>> >I tend to agree, but wonder if it would not make more sense to tackle this
>> >from a different angle.
>> >
>> >Consider all the programs that could clobber a mounted file system. Would
>> >it make more sense if we somehow protected a mounted disk device from
>> >being clobbered?
>>
>> Isn't this one of the things that secure_level > 0 protects you from?
>>
>> In fact, yes it is. (reference: page 263, 4.4BSD daemon book).
>>
>> >OTOH, this is a can of worms, no matter how you do it.
>
>Maybe I don't need to point this out, but...
>
>The thread started with some beginners who made a sad mistake. It seems to
>me that in order to set securelevel > 0, you need to know what you are
>doing. How do you protect the newbies who are not used to UNIX/FreeBSD
>and who therefore would not have any idea to set securelevel > 0..
Set it to default with securelevel > 0, but you can't.......
>We don't default to a securelevel > 0.
.....because of another can of worms that gets opened by securelevel > 0.
>> >OTOH, this is a can of worms, no matter how you do it.
^^ pretty much.
--
XCOMM Kevin P. Neal, Sophomore, Comp. Sci. \ kpneal@interpath.com
XCOMM "Corrected!" -- Old Amiga tips file \ kpneal@eos.ncsu.edu
XCOMM Visit the House of Retrocomputing: / Perm. Email:
XCOMM http://www4.ncsu.edu/~kpneal/www/ / kevinneal@bix.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1.5.4.32.19960814220314.0074ba08>