Bug 7001 – Invalid Windows Chars Mangled with unix extensions enabled (linux-linux sharing)

Bug 7001 - Invalid Windows Chars Mangled with unix extensions enabled (linux-linux sharing)


Summary:	Invalid Windows Chars Mangled with unix extensions enabled (linux-linux sharing)

Status:	NEW

Product:	Samba 3.4
Classification:	Unclassified
Component:	Client Tools
Version:	3.4.3
Hardware:	Other Linux

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Jeremy Allison
QA Contact:	Samba QA Contact

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-12-18 17:01 UTC by Shirakawasuna
Modified:	2009-12-19 15:26 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Shirakawasuna 2009-12-18 17:01:14 UTC

My setup: current archlinux systems, both the server and the client have samba version 3.4.3.  I'm sharing files (videos) with a simple setup and 'share' security privileges.  When viewing the share using either smbclient or KDE dolphin's smb:// protocol, invalid Windows chars like colons (":") or or question marks ("?") result in mangling.  I suspect libsmbclient as a result of both interfaces having this issue.  Mounting with CIFS does not mangle the filenames.

After asking on the samba irc channel on freenode, user kukks confirmed this behavior on the git version as of the 18th of December, 2009.  testparm indicates that unix extensions are enabled and I have attempted messing with the charset options several times (although I was informed this was not the problem), to no avail.

Comment 1 Derrell Lipman 2009-12-19 15:26:18 UTC

Contrary to the similar names, smbclient is not based on libsmbclient. The mangling occurs much deeper than either of those.

Jeremy, to you to work on or reassign.

Derrell