Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!okstate!uokmax!rmtodd
From: rmtodd@uokmax.UUCP (Richard Michael Todd)
Newsgroups: comp.os.minix
Subject: Re: Becoming ROOT on MINIX
Message-ID: <580@uokmax.UUCP>
Date: Sat, 23-May-87 22:36:04 EDT
Article-I.D.: uokmax.580
Posted: Sat May 23 22:36:04 1987
Date-Received: Sun, 24-May-87 03:43:53 EDT
References: <600@dutesta.UUCP> <832@ncsuvx.ncsu.edu> <397@bms-at.UUCP>
Organization: University of Oklahoma, Norman, OK
Lines: 23
Keywords: protection minix

In article <397@bms-at.UUCP>, stuart@bms-at.UUCP (Stuart D. Gathman) writes:
> 
> The mount program should check to see if the user has access to the
> block special file being mounted.  Set permissions for /dev/fd0 to
> 0600, and only root can mount/umount it.
> 
> If the current mount doesn't check this, just make mount executable
> by root only.
In a sense, it already is.  The code in fs/mount.c will only let root
execute the mount and unmount system calls.  Of course, in the default
distribution, /etc/mount and /etc/umount are set-uid root, which allows
anyone to use them.  A quick chmod will give you the behavior you want.

It shouldn't be too difficult to change mount and umount system calls
to check if the real user can access the device in question, and if you
want to give different logins different access priviledges, that's
probably the way to go.  Another thing you might want to keep in mind:
If I remember correctly, all the devices in /dev are owned by bin, not
root.
--------------------------------------------------------------------------
Richard Todd
USSnail:820 Annie Court,Norman OK 73069
UUCP: {allegra!cbosgd|ihnp4}!okstate!uokmax!rmtodd