Bug 53880

Summary:	Samba shares with consecutive whitespaces not working as expected
Product:	UCS	Reporter:	Jürn Brodersen <brodersen>
Component:	Samba4	Assignee:	Samba maintainers <samba-maintainers>
Status:	NEW ---	QA Contact:	Samba maintainers <samba-maintainers>
Severity:	normal
Priority:	P5
Version:	UCS 5.0
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=38688 https://forge.univention.org/bugzilla/show_bug.cgi?id=53799 https://forge.univention.org/bugzilla/show_bug.cgi?id=53800
What kind of report is it?:	Bug Report	What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains	How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.091	Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:

Description Jürn Brodersen

2021-10-06 14:45:16 CEST

Samba shares with consecutive whitespaces not working as expected

While Bug 38688 and Bug 53799 fixed a problem with loading the samba config then it contains shares with consecutive whitespaces, actual accessing such a share is still problematic or even doesn't work at all.

First samba seems to reduce consecutive whitespaces in share names to a single whitespace.
E.g. if the share is called "two  space", it is listed in samba (smbclient -L ...) as "two space" and can only be accessed as "two space". Accessing it using "two  space" results in the following error:
"tree connect failed: NT_STATUS_BAD_NETWORK_NAME" (using smbclient)
I could not find any documentation about this behavior.

Secondly if the directory which should be shared contains consecutive whitespaces, it seems impossible to access that share at all. Even if the share name has no spaces. Trying to access such a share results in the following error:
"tree connect failed: NT_STATUS_NO_SUCH_GROUP" (using smbclient)