[Eisfair] [e1] Samba 9.2.0 (Status 'stable')

[Thomas Bork]

Am 13.03.2020 um 07:35 schrieb B. Sprenger:

> Der Parameter hat nicht existiert.
> Also habe ich ihn eingefügt.
> Danach waren die Verzeichnisnamen wie gewohnt "verstümmelt", so das der 
> Zugriff wieder funktionierte.

Ok.

Erklärung:
Der Default für diesen Parameter wurde von 'yes' auf 'illegal verändert, 
wie in dem von mir geposteten Link in meinem Ursprungsposting 
nachzulesen ist:

https://www.samba.org/samba/history/samba-4.11.0.html

Das hatte ich bisher übersehen.
Dazu sagt die (nicht aktuelle) manpage von smb.conf unter

https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#NAMEMANGLING

mangled names (S)

     This controls whether non-DOS names under UNIX should be mapped to 
DOS-compatible names ("mangled") and made visible, or whether non-DOS 
names should simply be ignored.

     See the section on name mangling for details on how to control the 
mangling process.

     Possible option settings are

         yes (default) - enables name mangling for all not DOS 8.3 
conforming names.

         no - disables any name mangling.

         illegal - does mangling for names with illegal NTFS characters. 
This is the most sensible setting for modern clients that don't use the 
shortname anymore.

     If mangling is used then the mangling method is as follows:

         The first (up to) five alphanumeric characters before the 
rightmost dot of the filename are preserved, forced to upper case, and 
appear as the first (up to) five characters of the mangled name.

         A tilde "~" is appended to the first part of the mangled name, 
followed by a two-character unique sequence, based on the original root 
name (i.e., the original filename minus its final extension). The final 
extension is included in the hash calculation only if it contains any 
upper case characters or is longer than three characters.

         Note that the character to use may be specified using the 
mangling char option, if you don't like '~'.

         Files whose UNIX name begins with a dot will be presented as 
DOS hidden files. The mangled name will be created as for other 
filenames, but with the leading dot removed and "___" as its extension 
regardless of actual original extension (that's three underscores).

     The two-digit hash value consists of upper case alphanumeric 
characters.

     This algorithm can cause name collisions only if files in a 
directory share the same first five alphanumeric characters. The 
probability of such a clash is 1/1300.

     The name mangling (if enabled) allows a file to be copied between 
UNIX directories from Windows/DOS while retaining the long UNIX 
filename. UNIX files can be renamed to a new extension from Windows/DOS 
and will retain the same basename. Mangled names do not change between 
sessions.

     Default: mangled names = yes

     Example: mangled names = illegal

> Könnte man das evt. in die Konfiguration mit aufnehme?
> Vermutlich bin ich der einzige das so etwas benötigt. Aber sonst muss 
> ich bei jedem Update wieder daran denken den Parameter zu setzen.

Da die Einstellung 'mangled names = yes' nur für Uralt-Programme Sinn 
macht, werde ich ihn wohl in zukünftigen Samba-Versionen nur bei 
"SAMBA_COMPAT = yes" setzen - so ungern ich auch möchte, dass das 
überhaupt jemand benutzt.

Ich würde Dir statt dessen empfehlen, diesen Parameter per sambaexpert 
setzen zu lassen.

-- 
der tom
[eisfair-team]