Interestingly, I've noticed a difference between using mount.cifs setuid root (invoked as a normal user) and actually running mount.cifs as root, using sudo:
Note the difference between the reported uid and gid values. Perhaps this is a change in the way the kernel module behaves given a setuid root mount.cifs?
Interestingly, I've noticed a difference between using mount.cifs setuid root (invoked as a normal user) and actually running mount.cifs as root, using sudo:
mount.cifs --verbose -o rw,user= <domain> /rwh,uid= 1000,gid= 1000 //<fileserver> /<share> /<directory> /media/<share> ,unc=\\ <fileserver> \<share> ,noauto, uid=0,gid= 0,ver=1, user=rwh, domain= <domain> ,prefixpath= <directory> ,pass=* *******
Password:
mount.cifs kernel mount options: ip=<myip>
sudo mount.cifs --verbose -o rw,user= <domain> /rwh,uid= 1000,gid= 1000 //<fileserver> /<share> /<directory> /media/<share> ,unc=\\ <fileserver> \<share> ,uid=1000, gid=1000, ver=1,user= rwh,domain= <domain> ,prefixpath= <directory> ,pass=* *******
Password:
mount.cifs kernel mount options: ip=<myip>
Note the difference between the reported uid and gid values. Perhaps this is a change in the way the kernel module behaves given a setuid root mount.cifs?