Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!marque!gryphon!crash!ford
From: ford@crash.CTS.COM (Michael Ditto)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: UNIX PC Security (errata and such)
Message-ID: <1864@crash.CTS.COM>
Date: Wed, 14-Oct-87 20:57:13 EDT
Article-I.D.: crash.1864
Posted: Wed Oct 14 20:57:13 1987
Date-Received: Sat, 17-Oct-87 02:11:05 EDT
References: <64@quincy.UUCP>
Reply-To: ford@crash.CTS.COM (Michael Ditto)
Organization: Crash TS, El Cajon, CA
Lines: 24
Keywords: security, unix-pc
Summary: lddrv should not be set-uid
Xref: mnetor comp.sys.att:1498 comp.unix.wizards:4917

In article <64@quincy.UUCP> lenny@quincy.UUCP (Lenny Tropiano) writes:
>In my last article where I stated that /etc/lddrv/lddrv should be
>protected as 4750, instead of 4755, so not everyone can "allocate
>and deallocate system drivers..."  Well I found out that "ipcs" uses
>this to see if the ipc (interprocess communication) driver is loaded.

NOBODY except root will ever need to install or remove drivers using
/etc/lddrv/lddrv, so lddrv does not need to be set-uid to root.  Since
ipcs only does "/etc/lddrv/lddrv -q lipc" it does not need to be root
at all.

The best solution to the lddrv security problem is to do

	chmod 755 /etc/lddrv/lddrv

That way anyone can look at the settings, but only root can change them,
because the syslocal(2) system call only lets super-user change the
driver configuration.

-- 

Mike Ditto					-=] Ford [=-
P.O. Box 1721					ford@crash.CTS.COM
Bonita, CA 92002				ford%oz@prep.mit.ai.edu