Hi,
just to be able to plan: Will this be fixed in Hardy eventuall, or only
in newer releases?
Thanks,
Joachim
--
cifs does not support kerberos authentication
https://bugs.launchpad.net/bugs/236830
You received this bug notification because you are a member of Ubuntu
Server Team, which is
iI have linked a related Debian bug. This seems to be fixed in the new
openssh version 5.1, according to
http://packages.qa.debian.org/o/openssh/news/20080725T104703Z.html
Is this fix important enough to warrant a backport for hardy?
** Bug watch added: Debian Bug tracker #372680
I compiled openssh 5.1 from intrepid on hardy, but it still does not
work. Strangly, I’m no longer getting an error message from mod_pam that
setuid fails, although pam_unix reports that the session is actually
closed.
--
pam_mount unable to unmount needs root priv
Nevermind, it worked after all. The remaining problem was a left-over
/var/run/pam-mount file. It still doesn’t work for su, BTW.
--
pam_mount unable to unmount needs root priv
https://bugs.launchpad.net/bugs/117736
You received this bug notification because you are a member of Ubuntu
Server
Hi Mannheim,
are you sure this is caused by problems with missing root persmissions?
In my experience, when gdm this bug does not appear (e.g. cifs mounts
are unmounted properly), while it occurs when using ssh or su.
I’m assuming that your problem is a different bug.
Greetings,
Joachim
--
Passing -o user=$(echo Töst|iconv -t850) to mount.cifs instead of just
user=Töst gives a different error message:
mount error 6 = No such device or address
instead of
mount error 13 = Permission denied
which seems to indicate that this is indeed an encoding issue.
--
mount.cifs does not handle
And indeed, doing the same trick for the umlaut in the share name makes
mount.cifs successfully mount the share.
--
mount.cifs does not handle umlauts in usernames correctly
https://bugs.launchpad.net/bugs/414865
You received this bug notification because you are a member of Ubuntu
Server Team,
A work-around for me is to wrap the mount.cifs-call in
pam_mount.conf.xml with the attached script. I know that the quoting is
not perfect, so beware.
** Attachment added: argto850
http://launchpadlibrarian.net/30422184/argto850
--
mount.cifs does not handle umlauts in usernames correctly
Hi,
these options are already correct by default, as testparm -v says:
unix charset is UTF8, dos charset is 850 and display charset is LOCALE.
Since smbclient and gvfsd work just perfect with umlauts, I think the
problem is either the kernel module or mount.cifs.
Probably the kernel module, as
Just in case anyone reads this and stumbles over the same error in
gnome-vfs, I worked around it with the attached hack (it makes gnome-vfs
not query hal for device names from /proc/mounts that start with two
slashes).
--
mount.cifs does not handle umlauts in usernames correctly
** Attachment added: gnome-vfs-ignore-cifs.patch
http://launchpadlibrarian.net/32595200/gnome-vfs-ignore-cifs.patch
--
mount.cifs does not handle umlauts in usernames correctly
https://bugs.launchpad.net/bugs/414865
You received this bug notification because you are a member of Ubuntu
Server
Hi Chuck,
correct, the patch is only tangentially related to the cifs bug, listed
here as a helpful hint for other people. But the bug in the cifs file
system still prevails, so I’m not sure if Won't Fix is the right tag
here...
Greetings,
Joachim
--
mount.cifs does not handle umlauts in
12 matches
Mail list logo
