Re: [PATCH] FUSE - remove mount_max and user_allow_other moduleparameters

[Miklos Szeredi]

> Are you sure you want to do this?  Placing security checks inside a 
> userspace utility and allowing everyone to do it in the kernel means that 
> any user/hacker could compile their own version of fusermount without the 
> check and bypass your security...  

These checks were part of the mount procedure.  Since currently
mount() is a privileged operation, it makes no difference if the check
is made inside the kernel or in a (secure) suid userspace app.

> So if you really do not want users to be able to do this you must do
> it inside the kernel.

I'd very much prefer a solution, where in certain situations the
privileges required for mount() could be relaxed.  But this involves
more than just a few checks in the FUSE kernel module.

Thanks,
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/