From b58b856db5c5c2583a4bbe24ab39726efefb18a6 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Fri, 23 Feb 2001 04:34:24 +0000 Subject: more updates. Conversion almost done. 2 more man pages (then all the ASCII stuff) (This used to be commit 7247027e833616bfe9350253cc1e6cdb236b2cdf) --- docs/htmldocs/smbcacls.1.html | 531 +++++++++++++++++------- docs/htmldocs/smbpasswd.5.html | 521 ++++++++++++++--------- docs/htmldocs/smbpasswd.8.html | 917 ++++++++++++++++++++++++++++------------- 3 files changed, 1336 insertions(+), 633 deletions(-) (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index e75a5741e5..36f570f2a0 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -1,161 +1,378 @@ - - - - -smbcacls (1) - - - - -

- -

smbcacls (1)

Samba

22 Dec 2000

- - - -

NAME

- smbcacls - Set or get ACLs on an NT file or directory -

SYNOPSIS

- -

smbcacls //server/share filename [-U username] -[-A acls] [-M acls] -[-D acls] [-S acls] -[-C name] [-G name] -[-n] [-h] -

DESCRIPTION

- -

The smbcacls program manipulates NT Access Control Lists (ACLs) on -SMB file shares. -

OPTIONS

- -

The following options are available to the smbcacls program. The -format of ACLs is described in the section ACL FORMAT -

-A acls

Add the ACLs specified to the ACL list. Existing access control entries -are unchanged. -

-M acls

Modify the mask value (permissions) for the ACLs specified on the command -line. An error will be printed for each ACL specified that was not already -present in the ACL list. -

-D acls

Delete any ACLs specfied on the command line. An error will be printed for -each ACL specified that was not already present in the ACL list. -

-S acls

This command sets the ACLs on the file with only the ones specified on the -command line. All other ACLs are erased. Note that the ACL specified must -contain at least a revision, type, owner and group for the call to succeed. -

-U username

Specifies a username used to connect to the specified service. The -username may be of the form username in which case the user is -prompted to enter in a password and the workgroup specified in the -smb.conf file is used, or username%password -or DOMAIN\username%password and the password and workgroup names are -used as provided. -

-C name

The owner of a file or directory can be changed to the name given -using the -C option. The name can be a sid in the form S-1-x-y-z or a -name resolved against the server specified in the first argument. -

This command is a shortcut for -M OWNER:name. -

-G name

The group owner of a file or directory can be changed to the name given -using the -G option. The name can be a sid in the form S-1-x-y-z or a -name resolved against the server specified in the first argument. -

This command is a shortcut for -M GROUP:name. -

-n

This option displays all ACL information in numeric format. The default is -to convert SIDs to names and ACE types and masks to a readable string -format. -

-h

Print usage information on the smbcacls program -

ACL FORMAT

- -

The format of an ACL is one or more ACL entries separated by either -commas or newlines. An ACL entry is one of the following: -

+smbcaclssmbcacls
Name
smbcacls -- Set or get ACLs on an NT file or directory names
Synopsis
nmblookup {//server/share} {filename} [-U username] [-A acls] [-M acls] [-D acls] [-S acls] [-C name] [-G name] [-n] [-h]
DESCRIPTION
This tool is part of the Samba suite.
The smbcacls program manipulates NT Access Control Lists
+ (ACLs) on SMB file shares.
OPTIONS
The following options are available to the smbcacls program.
+ The format of ACLs is described in the section ACL FORMAT
-A acls
Add the ACLs specified to the ACL list. Existing
+ access control entries are unchanged.
-M acls
Modify the mask value (permissions) for the ACLs
+ specified on the command line. An error will be printed for each
+ ACL specified that was not already present in the ACL list
+
-D acls
Delete any ACLs specfied on the command line.
+ An error will be printed for each ACL specified that was not
+ already present in the ACL list.
-S acls
This command sets the ACLs on the file with
+ only the ones specified on the command line. All other ACLs are
+ erased. Note that the ACL specified must contain at least a revision,
+ type, owner and group for the call to succeed.
-U username
Specifies a username used to connect to the
+ specified service. The username may be of the form "username" in
+ which case the user is prompted to enter in a password and the
+ workgroup specified in the smb.conf file is
+ used, or "username%password" or "DOMAIN\username%password" and the
+ password and workgroup names are used as provided.
-C name
The owner of a file or directory can be changed
+ to the name given using the -C option.
+ The name can be a sid in the form S-1-x-y-z or a name resolved
+ against the server specified in the first argument.
This command is a shortcut for -M OWNER:name.
+
-G name
The group owner of a file or directory can
+ be changed to the name given using the -G
+ option. The name can be a sid in the form S-1-x-y-z or a name
+ resolved against the server specified n the first argument.
+
This command is a shortcut for -M GROUP:name.
-n
This option displays all ACL information in numeric
+ format. The default is to convert SIDs to names and ACE types
+ and masks to a readable string format.
-h
Print usage information on the smbcacls
+ program.
ACL FORMAT
The format of an ACL is one or more ACL entries separated by
+ either commas or newlines. An ACL entry is one of the following:

REVISION:<revision number>
OWNER:<sid or name>
GROUP:<sid or name>
ACL:<sid or name>:<type>/<flags>/<mask>
-
-
-The revision of the ACL specifies the internal Windows NT ACL revision for
-the security descriptor. If not specified it defaults to 1. Using values
-other than 1 may cause strange behaviour.
-
The owner and group specify the owner and group sids for the object. If a
-SID in the format S-1-x-y-z is specified this is used, otherwise
-the name specified is resolved using the server on which the file or
-directory resides.
-
ACLs specify permissions granted to the SID. This SID again can be
-specified in S-1-x-y-z format or as a name in which case it is resolved
-against the server on which the file or directory resides. The type, flags
-and mask values determine the type of access granted to the SID.
-
The type can be either 0 or 1 corresponding to ALLOWED or DENIED access to
-the SID. The flags values are generally zero for file ACLs and either 9 or
-2 for directory ACLs. Some common flags are:
-
-#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1
-#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2
-#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4
-#define SEC_ACE_FLAG_INHERIT_ONLY 0x8
-
-
-At present flags can only be specified as decimal or hexadecimal values.
-
The mask is a value which expresses the access right granted to the SID.
-It can be given as a decimal or hexadecimal value, or by using one of the
-following text strings which map to the NT file permissions of the same
-name.
-

-
R Allow read access
-
W Allow write access
-
X Execute permission on the object
-
D Delete the object
-
P Change permissions
-
O Take ownership
-
-The following combined permissions can be specified:
-

-
READ
-Equivalent to RX permissions
-
CHANGE
-Equivalent to RXWD permissions
-
FULL
-Equivalent to RWXDPO permissions
-

-
-
EXIT STATUS
-
-The smbcacls program sets the exit status depending on the success or
-otherwise of the operations performed. The exit status may be one of the
-following values.
-
If the operation succeded, smbcacls returns and exit status of 0. If
-smbcacls couldn't connect to the specified server, or there was an
-error getting or setting the ACLs, an exit status of 1 is returned. If
-there was an error parsing any command line arguments, an exit status of 2
-is returned.
-

-
AUTHOR
-
-The original Samba software and related utilities were created by
-Andrew Tridgell. Samba is now developed by the Samba Team as an Open
-Source project.
-
smbcacls was written by Andrew Tridgell and Tim Potter.
-
-
+

The revision of the ACL specifies the internal Windows + NT ACL revision for the security descriptor. + If not specified it defaults to 1. Using values other than 1 may + cause strange behaviour.

The owner and group specify the owner and group sids for the + object. If a SID in the format CWS-1-x-y-z is specified this is used, + otherwise the name specified is resolved using the server on which + the file or directory resides.

ACLs specify permissions granted to the SID. This SID again + can be specified in CWS-1-x-y-z format or as a name in which case + it is resolved against the server on which the file or directory + resides. The type, flags and mask values determine the type of + access granted to the SID.

The type can be either 0 or 1 corresponding to ALLOWED or + DENIED access to the SID. The flags values are generally + zero for file ACLs and either 9 or 2 for directory ACLs. Some + common flags are:

#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1
#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2
#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 +
#define SEC_ACE_FLAG_INHERIT_ONLY 0x8

At present flags can only be specified as decimal or + hexadecimal values.

The mask is a value which expresses the access right + granted to the SID. It can be given as a decimal or hexadecimal value, + or by using one of the following text strings which map to the NT + file permissions of the same name.

R - Allow read access
W - Allow write access
X - Execute permission on the object
D - Delete the object
P - Change permissions
O - Take ownership

The following combined permissions can be specified:

READ - Equivalent to 'RX' + permissions
CHANGE - Equivalent to 'RXWD' permissions +
FULL - Equivalent to 'RWXDPO' + permissions

EXIT STATUS

The smbcacls program sets the exit status + depending on the success or otherwise of the operations performed. + The exit status may be one of the following values.

If the operation succeded, smbcacls returns and exit + status of 0. If smbcacls couldn't connect to the specified server, + or there was an error getting or setting the ACLs, an exit status + of 1 is returned. If there was an error parsing any command line + arguments, an exit status of 2 is returned.

VERSION

This man page is correct for version 2.2 of + the Samba suite.

AUTHOR

The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed.

smbcacls was written by Andrew Tridgell + and Tim Potter.

The conversion to DocBook for Samba 2.2 was done + by Gerald Carter

\ No newline at end of file diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 2969022790..4ec7b7c86a 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -1,195 +1,326 @@ - - - - - - -smbpasswd (5) - - - - - -

- -

smbpasswd (5)

Samba

23 Oct 1998

- - - -

NAME

- smbpasswd - The Samba encrypted password file -

SYNOPSIS

- -

smbpasswd is the Samba encrypted password file. -

DESCRIPTION

- -

This file is part of the Samba suite. -

smbpasswd is the Samba encrypted password file. It contains -the username, Unix user id and the SMB hashed passwords of the -user, as well as account flag information and the time the password -was last changed. This file format has been evolving with Samba -and has had several different formats in the past. -

FILE FORMAT

- -

The format of the smbpasswd file used by Samba 2.0 is very similar to -the familiar Unix passwd (5) file. It is an ASCII file containing -one line for each user. Each field within each line is separated from -the next by a colon. Any entry beginning with # is ignored. The -smbpasswd file contains the following information for each user: -

name

This is the user name. It must be a name that already exists - in the standard UNIX passwd file. -

uid

This is the UNIX uid. It must match the uid field for the same - user entry in the standard UNIX passwd file. If this does not - match then Samba will refuse to recognize this smbpasswd file entry - as being valid for a user. -

Lanman Password Hash

This is the LANMAN hash of the users password, encoded as 32 hex - digits. The LANMAN hash is created by DES encrypting a well known - string with the users password as the DES key. This is the same - password used by Windows 95/98 machines. Note that this password hash - is regarded as weak as it is vulnerable to dictionary attacks and if - two users choose the same password this entry will be identical (i.e. - the password is not "salted" as the UNIX password is). If the - user has a null password this field will contain the characters - "NO PASSWORD" as the start of the hex string. If the hex string - is equal to 32 'X' characters then the users account is marked as - disabled and the user will not be able to log onto the Samba - server. -

WARNING !!. Note that, due to the challenge-response nature of the - SMB/CIFS authentication protocol, anyone with a knowledge of this - password hash will be able to impersonate the user on the network. - For this reason these hashes are known as "plain text equivalent" - and must NOT be made available to anyone but the root user. To - protect these passwords the smbpasswd file is placed in a - directory with read and traverse access only to the root user and the - smbpasswd file itself must be set to be read/write only by root, - with no other access. -

NT Password Hash

This is the Windows NT hash of the users password, encoded as 32 - hex digits. The Windows NT hash is created by taking the users - password as represented in 16-bit, little-endian UNICODE and then - applying the MD4 (internet rfc1321) hashing algorithm to it. -

This password hash is considered more secure than the Lanman - Password Hash as it preserves the case of the - password and uses a much higher quality hashing algorithm. However, it - is still the case that if two users choose the same password this - entry will be identical (i.e. the password is not "salted" as the - UNIX password is). -

Account Flags

This section contains flags that describe the attributes of the users - account. In the Samba2.0 release this field is bracketed by '[' - and ']' characters and is always 13 characters in length (including - the '[' and ']' characters). The contents of this field may be - any of the characters. -

'U' This means this is a "User" account, i.e. an ordinary - user. Only User and Workstation Trust accounts are - currently supported in the smbpasswd file. -

'N' This means the account has no password (the passwords - in the fields Lanman Password Hash and - NT Password Hash are ignored). Note that this - will only allow users to log on with no password if the - null passwords parameter is set - in the smb.conf (5) config file. -

'D' This means the account is disabled and no SMB/CIFS logins - will be allowed for this user. -

'W' This means this account is a "Workstation Trust" account. - This kind of account is used in the Samba PDC code stream to allow Windows - NT Workstations and Servers to join a Domain hosted by a Samba PDC. -

Other flags may be added as the code is extended in future. The rest of - this field space is filled in with spaces. -

Last Change Time

This field consists of the time the account was last modified. It consists of - the characters LCT- (standing for "Last Change Time") followed by a numeric - encoding of the UNIX time in seconds since the epoch (1970) that the last change - was made. -

Following fields

All other colon separated fields are ignored at this time. -

NOTES

- -

In previous versions of Samba (notably the 1.9.18 series) this file -did not contain the Account Flags or -Last Change Time fields. The Samba 2.0 -code will read and write these older password files but will not be able to -modify the old entries to add the new fields. New entries added with -smbpasswd (8) will contain the new fields -in the added accounts however. Thus an older smbpasswd file used -with Samba 2.0 may end up with some accounts containing the new fields -and some not. -

In order to convert from an old-style smbpasswd file to a new -style, run the script convert_smbpasswd, installed in the -Samba bin/ directory (the same place that the smbd -and nmbd binaries are installed) as follows: -

-
-
-    cat old_smbpasswd_file | convert_smbpasswd > new_smbpasswd_file
-
-
-

- -

The convert_smbpasswd script reads from stdin and writes to stdout -so as not to overwrite any files by accident. -

Once this script has been run, check the contents of the new smbpasswd -file to ensure that it has not been damaged by the conversion script -(which uses awk), and then replace the <old smbpasswd file> -with the <new smbpasswd file>. -

VERSION

- -

This man page is correct for version 2.0 of the Samba suite. -

AUTHOR

- -

The original Samba software and related utilities were created by -Andrew Tridgell samba@samba.org. Samba is now developed -by the Samba Team as an Open Source project similar to the way the -Linux kernel is developed. -

The original Samba man pages were written by Karl Auer. The man page -sources were converted to YODL format (another excellent piece of Open -Source software, available at -ftp://ftp.icce.rug.nl/pub/unix/) -and updated for the Samba2.0 release by Jeremy -Allison, samba@samba.org. -

See samba (7) to find out how to get a full -list of contributors and details on how to submit bug reports, -comments etc. - - +smbpasswd

smbpasswd

Name

smbpasswd -- The Samba encrypted password file

Synopsis

smbpasswd

DESCRIPTION

This tool is part of the Samba suite.

smbpasswd is the Samba encrypted password file. It contains + the username, Unix user id and the SMB hashed passwords of the + user, as well as account flag information and the time the + password was last changed. This file format has been evolving with + Samba and has had several different formats in the past.

FILE FORMAT

The format of the smbpasswd file used by Samba 2.2 + is very similar to the familiar Unix passwd(5) + file. It is an ASCII file containing one line for each user. Each field + ithin each line is separated from the next by a colon. Any entry + beginning with '#' is ignored. The smbpasswd file contains the + following information for each user:

name

This is the user name. It must be a name that + already exists in the standard UNIX passwd file.

uid

This is the UNIX uid. It must match the uid + field for the same user entry in the standard UNIX passwd file. + If this does not match then Samba will refuse to recognize + this smbpasswd file entry as being valid for a user. +

Lanman Password Hash

This is the LANMAN hash of the users password, + encoded as 32 hex digits. The LANMAN hash is created by DES + encrypting a well known string with the users password as the + DES key. This is the same password used by Windows 95/98 machines. + Note that this password hash is regarded as weak as it is + vulnerable to dictionary attacks and if two users choose the + same password this entry will be identical (i.e. the password + is not "salted" as the UNIX password is). If the user has a + null password this field will contain the characters "NO PASSWORD" + as the start of the hex string. If the hex string is equal to + 32 'X' characters then the users account is marked as + disabled and the user will not be able to + log onto the Samba server.

WARNING !! Note that, due to + the challenge-response nature of the SMB/CIFS authentication + protocol, anyone with a knowledge of this password hash will + be able to impersonate the user on the network. For this + reason these hashes are known as plain text + equivalents and must NOT be made + available to anyone but the root user. To protect these passwords + the smbpasswd file is placed in a directory with read and + traverse access only to the root user and the smbpasswd file + itself must be set to be read/write only by root, with no + other access.

NT Password Hash

This is the Windows NT hash of the users + password, encoded as 32 hex digits. The Windows NT hash is + created by taking the users password as represented in + 16-bit, little-endian UNICODE and then applying the MD4 + (internet rfc1321) hashing algorithm to it.

This password hash is considered more secure than + the Lanman Password Hash as it preserves the case of the + password and uses a much higher quality hashing algorithm. + However, it is still the case that if two users choose the same + password this entry will be identical (i.e. the password is + not "salted" as the UNIX password is).

WARNING !!. Note that, due to + the challenge-response nature of the SMB/CIFS authentication + protocol, anyone with a knowledge of this password hash will + be able to impersonate the user on the network. For this + reason these hashes are known as plain text + equivalents and must NOT be made + available to anyone but the root user. To protect these passwords + the smbpasswd file is placed in a directory with read and + traverse access only to the root user and the smbpasswd file + itself must be set to be read/write only by root, with no + other access.

Account Flags

This section contains flags that describe + the attributes of the users account. In the Samba 2.2 release + this field is bracketed by '[' and ']' characters and is always + 13 characters in length (including the '[' and ']' characters). + The contents of this field may be any of the characters. +

U - This means + this is a "User" account, i.e. an ordinary user. Only User + and Workstation Trust accounts are currently supported + in the smbpasswd file.
N - This means the + account has no password (the passwords in the fields Lanman + Password Hash and NT Password Hash are ignored). Note that this + will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(5) + config file.
D - This means the account + is disabled and no SMB/CIFS logins will be allowed for + this user.
W - This means this account + is a "Workstation Trust" account. This kind of account is used + in the Samba PDC code stream to allow Windows NT Workstations + and Servers to join a Domain hosted by a Samba PDC.

Other flags may be added as the code is extended in future. + The rest of this field space is filled in with spaces.

Last Change Time

This field consists of the time the account was + last modified. It consists of the characters 'LCT-' (standing for + "Last Change Time") followed by a numeric encoding of the UNIX time + in seconds since the epoch (1970) that the last change was made. +

All other colon separated fields are ignored at this time.

VERSION

This man page is correct for version 2.2 of + the Samba suite.

AUTHOR

The original Samba man pages were written by Karl Auer. + The man page sources were converted to YODL format (another + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter

\ No newline at end of file diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index a0f4577b08..8fb2c580e7 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -1,281 +1,636 @@ - - - - - - -smbpasswd (8) - - - - - -

- -

smbpasswd (8)

Samba

23 Oct 1998

- - - -

NAME

- smbpasswd - change a users SMB password -

SYNOPSIS

- -

smbpasswd [-a] [-x] [-d] [-e] [-D debug level] [-n] [-r remote_machine] [-R name resolve order] [-m] [-j DOMAIN] [-U username] [-h] [-s] username -

DESCRIPTION

- -

This program is part of the Samba suite. -

The smbpasswd program has several different functions, depending -on whether it is run by the root user or not. When run as a normal -user it allows the user to change the password used for their SMB -sessions on any machines that store SMB passwords. -

By default (when run with no arguments) it will attempt to change the -current users SMB password on the local machine. This is similar to -the way the passwd (1) program works. smbpasswd differs from how -the passwd program works however in that it is not setuid root -but works in a client-server mode and communicates with a locally -running smbd. As a consequence in order for this -to succeed the smbd daemon must be running on -the local machine. On a UNIX machine the encrypted SMB passwords are -usually stored in the smbpasswd (5) file. -

When run by an ordinary user with no options. smbpasswd will -prompt them for their old smb password and then ask them for their new -password twice, to ensure that the new password was typed -correctly. No passwords will be echoed on the screen whilst being -typed. If you have a blank smb password (specified by the string "NO -PASSWORD" in the smbpasswd file) then just -press the <Enter> key when asked for your old password. -

smbpasswd can also be used by a normal user to change their SMB -password on remote machines, such as Windows NT Primary Domain -Controllers. See the (-r) and --U options below. -

When run by root, smbpasswd allows new users to be added and -deleted in the smbpasswd file, as well as -allows changes to the attributes of the user in this file to be made. When -run by root, smbpasswd accesses the local -smbpasswd file directly, thus enabling -changes to be made even if smbd is not running. -

OPTIONS

- -

-a

This option specifies that the username following should -be added to the local smbpasswd file, with -the new password typed (type <Enter> for the old password). This -option is ignored if the username following already exists in the -smbpasswd file and it is treated like a -regular change password command. Note that the user to be added -must already exist in the system password file (usually /etc/passwd) -else the request to add the user will fail. -

This option is only available when running smbpasswd as -root. -

-x

This option specifies that the username following should -be deleted from the local smbpasswd file. -

This option is only available when running smbpasswd as -root. -

-d

This option specifies that the username following should be -disabled in the local smbpasswd file. -This is done by writing a 'D' flag into the account control space -in the smbpasswd file. Once this is done -all attempts to authenticate via SMB using this username will fail. -

If the smbpasswd file is in the 'old' -format (pre-Samba 2.0 format) there is no space in the users password -entry to write this information and so the user is disabled by writing -'X' characters into the password space in the -smbpasswd file. See smbpasswd -(5) for details on the 'old' and new password file -formats. -

This option is only available when running smbpasswd as root. -

-e

This option specifies that the username following should be -enabled in the local smbpasswd file, -if the account was previously disabled. If the account was not -disabled this option has no effect. Once the account is enabled -then the user will be able to authenticate via SMB once again. -

If the smbpasswd file is in the 'old' format then smbpasswd will -prompt for a new password for this user, otherwise the account will be -enabled by removing the 'D' flag from account control space in the -smbpasswd file. See smbpasswd -(5) for details on the 'old' and new password file -formats. -

This option is only available when running smbpasswd as root. -

-D debuglevel

debuglevel is an integer from 0 -to 10. The default value if this parameter is not specified is zero. -

The higher this value, the more detail will be logged to the log files -about the activities of smbpasswd. At level 0, only critical errors -and serious warnings will be logged. -

Levels above 1 will generate considerable amounts of log data, and -should only be used when investigating a problem. Levels above 3 are -designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. -

-n

This option specifies that the username following should -have their password set to null (i.e. a blank password) in the local -smbpasswd file. This is done by writing the -string "NO PASSWORD" as the first part of the first password stored in -the smbpasswd file. -

Note that to allow users to logon to a Samba server once the password -has been set to "NO PASSWORD" in the -smbpasswd file the administrator must set -the following parameter in the [global] section of the -smb.conf file : -

null passwords = true -

This option is only available when running smbpasswd as root. -

-r remote machine name

This option allows a -user to specify what machine they wish to change their password -on. Without this parameter smbpasswd defaults to the local -host. The "remote machine name" is the NetBIOS name of the -SMB/CIFS server to contact to attempt the password change. This name -is resolved into an IP address using the standard name resolution -mechanism in all programs of the Samba -suite. See the -R name resolve order parameter for details on changing this resolving -mechanism. -

The username whose password is changed is that of the current UNIX -logged on user. See the -U username -parameter for details on changing the password for a different -username. -

Note that if changing a Windows NT Domain password the remote machine -specified must be the Primary Domain Controller for the domain (Backup -Domain Controllers only have a read-only copy of the user account -database and will not allow the password change). -

Note that Windows 95/98 do not have a real password database -so it is not possible to change passwords specifying a Win95/98 -machine as remote machine target. -

-R name resolve order

This option allows the user of -smbclient to determine what name resolution services to use when -looking up the NetBIOS name of the host being connected to. -

The options are :"lmhosts", "host", -"wins" and "bcast". They cause names to be -resolved as follows : -

lmhosts : Lookup an IP address in the Samba lmhosts file. -

host : Do a standard host name to IP address resolution, -using the system /etc/hosts, NIS, or DNS lookups. This method of name -resolution is operating system dependent. For instance on IRIX or -Solaris, this may be controlled by the /etc/nsswitch.conf file). -

wins : Query a name with the IP address listed in the -wins server parameter in the -smb.conf file. If -no WINS server has been specified this method will be ignored. -

bcast : Do a broadcast on each of the known local interfaces -listed in the interfaces parameter -in the smb.conf file. This is the least reliable of the name resolution -methods as it depends on the target host being on a locally connected -subnet. -

If this parameter is not set then the name resolve order defined -in the smb.conf file parameter -name resolve order -will be used. -

The default order is lmhosts, host, wins, bcast and without this -parameter or any entry in the smb.conf -file the name resolution methods will be attempted in this order. -

-m

This option tells smbpasswd that the account being -changed is a MACHINE account. Currently this is used when Samba is -being used as an NT Primary Domain Controller. PDC support is not a -supported feature in Samba2.0 but will become supported in a later -release. If you wish to know more about using Samba as an NT PDC then -please subscribe to the mailing list -samba-ntdom@samba.org. -

This option is only available when running smbpasswd as root. -

-j DOMAIN

This option is used to add a Samba server into a -Windows NT Domain, as a Domain member capable of authenticating user -accounts to any Domain Controller in the same way as a Windows NT -Server. See the security=domain -option in the smb.conf (5) man page. -

In order to be used in this way, the Administrator for the Windows -NT Domain must have used the program "Server Manager for Domains" -to add the primary NetBIOS name of -the Samba server as a member of the Domain. -

After this has been done, to join the Domain invoke smbpasswd with -this parameter. smbpasswd will then look up the Primary Domain -Controller for the Domain (found in the -smb.conf file in the parameter -password server and change -the machine account password used to create the secure Domain -communication. This password is then stored by smbpasswd in a -file, read only by root, called <Domain>.<Machine>.mac where -<Domain> is the name of the Domain we are joining and <Machine> -is the primary NetBIOS name of the machine we are running on. -

Once this operation has been performed the -smb.conf file may be updated to set the -security=domain option and all -future logins to the Samba server will be authenticated to the Windows -NT PDC. -

Note that even though the authentication is being done to the PDC all -users accessing the Samba server must still have a valid UNIX account -on that machine. -

This option is only available when running smbpasswd as root. -

-U username

This option may only be used in -conjunction with the -r -option. When changing a password on a remote machine it allows the -user to specify the user name on that machine whose password will be -changed. It is present to allow users who have different user names on -different systems to change these passwords. -

-h

This option prints the help string for smbpasswd, -selecting the correct one for running as root or as an ordinary user. -

-s

This option causes smbpasswd to be silent (i.e. not -issue prompts) and to read it's old and new passwords from standard -input, rather than from /dev/tty (like the passwd (1) program -does). This option is to aid people writing scripts to drive smbpasswd -

username

This specifies the username for all of the root -only options to operate on. Only root can specify this parameter as -only root has the permission needed to modify attributes directly -in the local smbpasswd file. -

NOTES

- -

Since smbpasswd works in client-server mode communicating with a -local smbd for a non-root user then the smbd -daemon must be running for this to work. A common problem is to add a -restriction to the hosts that may access the smbd running on the -local machine by specifying a "allow -hosts" or "deny -hosts" entry in the -smb.conf file and neglecting to allow -"localhost" access to the smbd. -

In addition, the smbpasswd command is only useful if Samba has -been set up to use encrypted passwords. See the file ENCRYPTION.txt -in the docs directory for details on how to do this. -

VERSION

- -

This man page is correct for version 2.0 of the Samba suite. -

AUTHOR

- -

See samba (7) to find out how to get a full -list of contributors and details on how to submit bug reports, -comments etc. - - +smbpasswd

smbpasswd

Name

smbpasswd -- change a users SMB password

Synopsis

smbpasswd [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-j DOMAIN] [-U username] [-h] [-s] [username]

DESCRIPTION

This tool is part of the Samba suite.

The smbpasswd program has several different + functions, depending on whether it is run by the root + user or not. When run as a normal user it allows the user to change + the password used for their SMB sessions on any machines that store + SMB passwords.

By default (when run with no arguments) it will attempt to + change the current users SMB password on the local machine. This is + similar to the way the passwd(1) program works. + smbpasswd differs from how the passwd program works + however in that it is not setuid root but works in + a client-server mode and communicates with a locally running + smbd(8). As a consequence in order for this to + succeed the smbd daemon must be running on the local machine. On a + UNIX machine the encrypted SMB passwords are usually stored in + the smbpasswd(5) file.

When run by an ordinary user with no options. smbpasswd + will prompt them for their old smb password and then ask them + for their new password twice, to ensure that the new password + was typed correctly. No passwords will be echoed on the screen + whilst being typed. If you have a blank smb password (specified by + the string "NO PASSWORD" in the smbpasswd file) then just press + the <Enter> key when asked for your old password.

smbpasswd can also be used by a normal user to change their + SMB password on remote machines, such as Windows NT Primary Domain + Controllers. See the (-r) and -U options below.

When run by root, smbpasswd allows new users to be added + and deleted in the smbpasswd file, as well as allows changes to + the attributes of the user in this file to be made. When run by root, + smbpasswd accesses the local smbpasswd file + directly, thus enabling changes to be made even if smbd is not + running.

OPTIONS

-a

This option specifies that the username + following should be added to the local smbpasswd file, with the + new password typed (type <Enter> for the old password). This + option is ignored if the username following already exists in + the smbpasswd file and it is treated like a regular change + password command. Note that the user to be added must already exist + in the system password file (usually /etc/passwd) + else the request to add the user will fail.

This option is only available when running smbpasswd + as root.

-x

This option specifies that the username + following should be deleted from the local smbpasswd file. +

This option is only available when running smbpasswd as + root.

-d

This option specifies that the username following + should be disabled in the local smbpasswd + file. This is done by writing a 'D' flag + into the account control space in the smbpasswd file. Once this + is done all attempts to authenticate via SMB using this username + will fail.

If the smbpasswd file is in the 'old' format (pre-Samba 2.0 + format) there is no space in the users password entry to write + this information and so the user is disabled by writing 'X' characters + into the password space in the smbpasswd file. See smbpasswd(5) + for details on the 'old' and new password file formats. +

This option is only available when running smbpasswd as + root.

-e

This option specifies that the username following + should be enabled in the local smbpasswd file, + if the account was previously disabled. If the account was not + disabled this option has no effect. Once the account is enabled then + the user will be able to authenticate via SMB once again.

If the smbpasswd file is in the 'old' format, then smbpasswd will prompt for a new password for this user, + otherwise the account will be enabled by removing the 'D' + flag from account control space in the smbpasswd file. See smbpasswd (5) for + details on the 'old' and new password file formats.

This option is only available when running smbpasswd as root. +

-D debuglevel

debuglevel is an integer + from 0 to 10. The default value if this parameter is not specified + is zero.

The higher this value, the more detail will be logged to the + log files about the activities of smbpasswd. At level 0, only + critical errors and serious warnings will be logged.

Levels above 1 will generate considerable amounts of log + data, and should only be used when investigating a problem. Levels + above 3 are designed for use only by developers and generate + HUGE amounts of log data, most of which is extremely cryptic. +

-n

This option specifies that the username following + should have their password set to null (i.e. a blank password) in + the local smbpasswd file. This is done by writing the string "NO + PASSWORD" as the first part of the first password stored in the + smbpasswd file.

Note that to allow users to logon to a Samba server once + the password has been set to "NO PASSWORD" in the smbpasswd + file the administrator must set the following parameter in the [global] + section of the smb.conf file :

null passwords = yes

This option is only available when running smbpasswd as + root.

-r remote machine name

This option allows a user to specify what machine + they wish to change their password on. Without this parameter + smbpasswd defaults to the local host. The remote + machine name is the NetBIOS name of the SMB/CIFS + server to contact to attempt the password change. This name is + resolved into an IP address using the standard name resolution + mechanism in all programs of the Samba suite. See the -R + name resolve order parameter for details on changing + this resolving mechanism.

The username whose password is changed is that of the + current UNIX logged on user. See the -U username + parameter for details on changing the password for a different + username.

Note that if changing a Windows NT Domain password the + remote machine specified must be the Primary Domain Controller for + the domain (Backup Domain Controllers only have a read-only + copy of the user account database and will not allow the password + change).

Note that Windows 95/98 do not have + a real password database so it is not possible to change passwords + specifying a Win95/98 machine as remote machine target.

-R name resolve order

This option allows the user of smbclient to determine + what name resolution services to use when looking up the NetBIOS + name of the host being connected to.

The options are :"lmhosts", "host", "wins" and "bcast". They cause + names to be resolved as follows :

lmhosts : Lookup an IP + address in the Samba lmhosts file. If the line in lmhosts has + no name type attached to the NetBIOS name (see the lmhosts(5) for details) then + any name type matches for lookup.
host : Do a standard host + name to IP address resolution, using the system /etc/hosts +, NIS, or DNS lookups. This method of name resolution + is operating system depended for instance on IRIX or Solaris this + may be controlled by the /etc/nsswitch.conf + file). Note that this method is only used if the NetBIOS name + type being queried is the 0x20 (server) name type, otherwise + it is ignored.
wins : Query a name with + the IP address listed in the wins server + parameter. If no WINS server has been specified this method + will be ignored.
bcast : Do a broadcast on + each of the known local interfaces listed in the + interfaces parameter. This is the least + reliable of the name resolution methods as it depends on the + target host being on a locally connected subnet.

The default order is lmhosts, host, wins, bcast + and without this parameter or any entry in the + smb.conf file the name resolution methods will + be attempted in this order.

-m

This option tells smbpasswd that the account + being changed is a MACHINE account. Currently this is used + when Samba is being used as an NT Primary Domain Controller.

This option is only available when running smbpasswd as root. +

-j DOMAIN

This option is used to add a Samba server + into a Windows NT Domain, as a Domain member capable of authenticating + user accounts to any Domain Controller in the same way as a Windows + NT Server. See the security = domain option in + the smb.conf(5) man page.

In order to be used in this way, the Administrator for + the Windows NT Domain must have used the program "Server Manager + for Domains" to add the primary NetBIOS name of the Samba server + as a member of the Domain.

After this has been done, to join the Domain invoke smbpasswd with this parameter. smbpasswd will then + look up the Primary Domain Controller for the Domain (found in + the smb.conf file in the parameter + password server and change the machine account + password used to create the secure Domain communication. This + password is then stored by smbpasswd in a TDB, writeable only by root, + called secrets.tdb

Once this operation has been performed the smb.conf file may be updated to set the security = domain option and all future logins + to the Samba server will be authenticated to the Windows NT + PDC.

Note that even though the authentication is being + done to the PDC all users accessing the Samba server must still + have a valid UNIX account on that machine.

This option is only available when running smbpasswd as root. +

-U username

This option may only be used in conjunction + with the -r option. When changing + a password on a remote machine it allows the user to specify + the user name on that machine whose password will be changed. It + is present to allow users who have different user names on + different systems to change these passwords.

-h

This option prints the help string for smbpasswd, selecting the correct one for running as root + or as an ordinary user.

-s

This option causes smbpasswd to be silent (i.e. + not issue prompts) and to read it's old and new passwords from + standard input, rather than from /dev/tty + (like the passwd(1) program does). This option + is to aid people writing scripts to drive smbpasswd

username

This specifies the username for all of the + root only options to operate on. Only root + can specify this parameter as only root has the permission needed + to modify attributes directly in the local smbpasswd file. +

NOTES

Since smbpasswd works in client-server + mode communicating with a local smbd for a non-root user then + the smbd daemon must be running for this to work. A common problem + is to add a restriction to the hosts that may access the smbd running on the local machine by specifying a + allow hosts or deny hosts + entry in the smb.conf file and neglecting to + allow "localhost" access to the smbd.

In addition, the smbpasswd command is only useful if Samba + has been set up to use encrypted passwords. See the file + ENCRYPTION.txt in the docs directory for details + on how to do this.

VERSION

This man page is correct for version 2.2 of + the Samba suite.

AUTHOR

\ No newline at end of file -- cgit

smbcacls (1)

Samba

22 Dec 2000

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

ACL FORMAT

smbcacls

Name

Synopsis

DESCRIPTION

OPTIONS

ACL FORMAT

EXIT STATUS

AUTHOR

EXIT STATUS

VERSION

AUTHOR

smbpasswd (5)

Samba

23 Oct 1998

NAME

SYNOPSIS

DESCRIPTION

FILE FORMAT

NOTES

VERSION

SEE ALSO

AUTHOR

smbpasswd

Name

Synopsis

DESCRIPTION

FILE FORMAT

VERSION

SEE ALSO

AUTHOR

smbpasswd (8)

Samba

23 Oct 1998

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

NOTES

VERSION

AUTHOR

smbpasswd

Name

Synopsis

DESCRIPTION

OPTIONS

NOTES

VERSION

SEE ALSO

AUTHOR