On Fri, Sep 03, 1999 at 03:01:26AM +0800, [EMAIL PROTECTED] wrote:
> > The user would still have to know what type of filesystem is on
> > the volume. My code tries filesystem types from a list, one by
> > one, so the same command or desktop icon will mount a FAT, UFS, or
> > EXT2FS floppy, for example. The system administrator can also
> > specify default mount options on a device or filesystem-type basis.
>
> I like that idea, but that still doesn't need suid privs to do.
But the mount call does. I agree that you need to specify the
mount restrictions centrally. Otherwise what's to prevent me (the
user) from making a floppy with a suid shell, and mounting it?
It makes sense in some situations for only the user on the console
to be able to perform mount operations, and to own the files once
they get mounted. This is essential for a lab environment. If
the options aren't appropriate for you, then configure things
differently.
Real configuration files are needed for this functionality. I
don't buy that getting the config into/out-of the kernel is
easier/better than a carefully crafted suid binary.
If someone wants to propose an alternate mount API into the kernel
that would provide for this functionality... that might be the best
of both worlds... I've not looked at the problem in much detail
though, but it would seem to address some concerns and keep the
features that Mr. Korty has implemented and contributed.
This still doesn't entirely
- Steve
--
WaterSpout Communications, Inc. [EMAIL PROTECTED]
427 North 6th Street http://www.waterspout.com/
Lafayette, IN 47901
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
