From 1e6e5b299c235b513095a76a4cd9fffc41e8fc9c Mon Sep 17 00:00:00 2001
From: Gerald Carter
Note that this paramater is not available when Samba listens + on port 445, as clients no longer send this information
controls the algorithm used for the generating + the mangled names. Can take two different values, "hash" and + "hash2". "hash" is the default and is the algorithm that has been + used in Samba for many years. "hash2" is a newer and considered + a better algorithm (generates less collisions) in the names. + However, many Win32 applications store the + mangled names and so changing to the new algorithm must not be done + lightly as these applications may break unless reinstalled. + New installations of Samba may set the default to hash2. + Default hash.
This specifies the major and minor version numbers
that nmbd will use when announcing itself as a server. The default
- is 4.2. Do not change this parameter unless you have a specific
+ is 4.5. Do not change this parameter unless you have a specific
need to set a Samba server to be a downlevel server. Default: See the discussion in the section NAME MANGLING. See the section on NAME MANGLING. Also note the If this parameter is set, a Windows NT ACL that contains
+ an unknown SID (security descriptor, or representation of a user or group id)
+ as the owner or group owner of the file will be silently mapped into the
+ current UNIX uid or gid of the currently connected user. This is designed to allow Windows NT clients to copy files and
+ folders containing ACLs that were created locally on the client machine
+ and contain users local to that machine only (no domain users) to be
+ copied to a Samba server (usually with XCOPY /O) and have the unknown
+ userid and groupid of the file owner map to the current connected user.
+ This can only be fixed correctly when winbindd allows arbitrary mapping
+ from any Windows NT SID to a UNIX uid or gid. Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
+ See also force group
+ Default: False Example: force unknown acl user = yes Default : ldap port = 636ldap port = 636 ; if ldap ssl = on Default : ldap port = 389 ; if ldap ssl = off See the section on NAME MANGLING See the section on NAME MANGLING for details on how to control the mangling process. If mangling is used then the mangling algorithm is as follows: If mangling algorithm "hash2" is used then the mangling algorithm is as follows: The first alphanumeric character
+ before the rightmost dot of the filename is preserved, forced
+ to upper case, and appears as the first character of the mangled name.
+ A base63 hash of 5 characters is generated and the
+ first 4 characters of that hash are appended to the first character.
+ A tilde "~" is appended to the first part of the mangled
+ name, followed by the final character of the base36 hash of the name.
+ Note that the character to use may be specified using
+ the mangling char
+ option, if you don't like '~'. The first three alphanumeric characters of the final
+ extension are preserved, forced to upper case and appear as the
+ extension of the mangled name. The final extension is defined as that
+ part of the original filename after the rightmost dot. If there are no
+ dots in the filename, the mangled name will have no extension (except
+ in the case of "hidden files" - see below). 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 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
@@ -11497,7 +11643,7 @@ NAME="MANGLINGCHAR"
the magic character in name mangling. The default is a '~'
but this may interfere with some software. Use this option to set
@@ -11515,6 +11661,33 @@ CLASS="COMMAND"
> controls the algorithm used for the generating
+ the mangled names. Can take two different values, "hash" and
+ "hash2". "hash" is the default and is the algorithm that has been
+ used in Samba for many years. "hash2" is a newer and considered
+ a better algorithm (generates less collisions) in the names.
+ However, many Win32 applications store the mangled names and so
+ changing to the new algorithm must not be done
+ lightly as these applications may break unless reinstalled.
+ New installations of Samba may set the default to hash2. Default: mangling method = hash Example: mangling method = hash2 See the section on NAME
MANGLING for a fuller discussion. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. parameter for details on doing this. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. parameter for details on doing this. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. See the section on NAME MANGLING. strip dot (G) This is a boolean that controls whether to
- strip trailing dots off UNIX filenames. This helps with some
- CDROMs that have filenames ending in a single dot. Default: See the section NOTE ABOUT
USERNAME/PASSWORD VALIDATION for more information on how
@@ -19019,24 +19194,32 @@ CLASS="COMMAND"
> This option controls whether or not smbd
- should lookup 'username' as 'DOMAIN\username' when winbindd is
- running on a system. This is most useful when used in conjunction
- with pam_winbind.so to prevent a Windows user from having to enter
- commands like "ssh 'DOMAIN\username@hostname'". This option is disabled
- by default, thus requiring that the DOMAIN\username format be used. Default: winbind use default domain = no
- Example: winbind use default domain = trueCOMPLETE LIST OF SERVICE PARAMETERS
EXPLANATION OF EACH PARAMETER