> On Wed, 1 Sep 1999 adr...@freebsd.org wrote: > > > On Tue, Aug 31, 1999, Doug Rabson wrote: > > > On Mon, 30 Aug 1999, Andrew J. Korty wrote: > > > > > > > I provided a solution via send-pr (bin/11031) over four months ago, > > > > which is, in my opinion, superior in many ways to this sysctl > > > > approach. The patch contains an amendment to the mount(1) manual > > > > page. > > > > > > I have not reviewed this pr myself but it seems like a well thought out > > > change to the system. Would the people who are involved with the current > > > (more limited) proposed change like to review this and possibly use it > > > instead. I don't want to lose anyones work here if it could be useful. > > > > You realise that this kind of stuff can be done in kernelspace, > > without needing yet another setuid binary/binaries.. > > Well, sysctl with list of pathes for user mounts looks good. > Configuration is simple and can be easliy changed at runtime. It is > always better to avoid setuid'ed binaries, this is more worse that > mount(8) can execute other mount_* binaries.
My code provides needed features that all implementations I've seen of the sysctl approach do not. Our users need to mount removable volumes just by clicking on a KDE icon, without having to know what type of filesystem is present on the media. Non-console users should not be permitted to mount removable volumes. Both of these features are provided by my patch, which I have had in production since I submitted it. The possibility of executing undesired mount_* binaries is precluded by the ability to list in the configuration file what filesystem types should be tried for each device. Andrew J. Korty, Director http://www.physics.purdue.edu/~ajk/ Physics Computer Network 85 73 1F 04 63 D9 9D 65 Purdue University 65 2E 7A A8 81 8C 45 75 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
