This bug is still unfixed, and it causes problems not only for passwords, but for the record name too.
# mount.cifs "\\\\record\\with\\comma\\in, name" ./mountpoint mount error(22) Invalid Argument In /var/log/kern.log CIFS: Unknown Mount option " name" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1069915 Title: unable to mount CIFS share with comma in password Status in cifs-utils package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since the update to Quantal I am unable to mount CIFS shares with a comma in the password: root@lama ~ # PASSWD=",password" mount -t cifs //cifs.example.org target -o username=user,domain=dom,uid=4711,gid=12345 mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) 32 root@lama ~ # dmesg | tail -1 [17848.954253] CIFS: Unknown mount option "password" The same thing happens with a credential file and the password prompt. This looks like a parser regression: mount.cifs(8) explains: Note that a password which contains the delimiter character (i.e. a comma ´,´) will fail to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or via a credentials file (see below) or entered at the password prompt will be read correctly. This is pretty evil, as it exposes parts of the password through dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1069915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
