Comment 4 for bug 657900

I also encountered this on upgrade from 10.04 to 10.10, and had previously used the setuid workaround mentioned by Ian Beardslee for 10.04.

For me, mounting as root is not satisfactory. It seems to me that forcing mount as root breaks Kerberos authentication (-o sec=krb5, which used to work), which in turn breaks single-sign-on for CIFS mounts.

Is it a bigger security risk to allow users to run mount.cifs with setuid or to force users to store their passwords on the disk?