![](https://seccdn.libravatar.org/avatar/6dbd124e7bd14fb899ae5f1d8e9b48f0.jpg?s=120&d=mm&r=g)
-----Original Message----- From: David C. Rankin [mailto:drankinatty@suddenlinkmail.com] Sent: Wednesday, May 07, 2008 3:28 PM To: suse Subject: Re: [opensuse] smbfs vs. cifs mounts to samba shares
<snip>
The noacl, noperm parameters tells the client side to let the server side handle setting/checking of permissions and ownership, which is what you want for a samba server, the way its always been, and the only way that really works for most environments.
I would suggest a closer look at the 'man mount.cifs' comments for noperm, as this could be a security issue in a multiuser environment. Though giving access via fstab does kind of make things global on the client. (For a per user option there is pam.mount).
I have being using the uid and guid option with setuids for some time without issues (except a possible latency issue). In my case uid and gid are probably redundant but setuids sets up a form of dynamic local permission cache.
Look at man mount.cifs again for more info...
and
http://pserver.samba.org/samba/ftp/cifs-cvs/linux-cifs-client-guide.pdf
may help...
WARNING, WARNING, the use of ,noperm will give root access to all cifs mounted shares mounted with the ,noperm options. A stray chmod -R or the like above the mount point will work all the way down the mounted client as well... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thanks David. So what is a better way to mount with cifs, instead of resorting back to smbfs? Use noacl and not noperm? Best regards, ~James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org