From 32a965e09ce4befe971855e11e1fb5ceb51a9ed1 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Mon, 13 Dec 1999 13:35:20 +0000 Subject: 2nd phase of head branch sync with SAMBA_2_0 - this delets all the files that were in the head branch but weren't in SAMBA_2_0 (This used to be commit d7b208786590b5a28618590172b8d523627dda09) --- docs/htmldocs/LDAP.html | 147 --------- docs/htmldocs/debug2html.1.html | 68 ----- docs/htmldocs/rpcclient.1.html | 651 ---------------------------------------- 3 files changed, 866 deletions(-) delete mode 100644 docs/htmldocs/LDAP.html delete mode 100644 docs/htmldocs/debug2html.1.html delete mode 100644 docs/htmldocs/rpcclient.1.html (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/LDAP.html b/docs/htmldocs/LDAP.html deleted file mode 100644 index 1cc8f8213f..0000000000 --- a/docs/htmldocs/LDAP.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - -LDAP Support in Samba - - - - - -
- -

LDAP Support in Samba

-

Matthew Chapman

-

29th November 1998 -

-WARNING: This is experimental code. Use at your own risk, and please report -any bugs (after reading BUGS.txt). -


- - - -

1: What is LDAP?

 -

2: Why LDAP and Samba?

 -

3: Using LDAP with Samba

 -

4: Using LDAP for Unix authentication

 -

5: Compatibility with Active Directory

 - -


-

- -

1: What is LDAP?

-A directory is a type of hierarchical database optimised for simple query -operations, often used for storing user information. LDAP is the -Lightweight Directory Access Protocol, a protocol which is rapidly -becoming the Internet standard for accessing directories.

- Many client applications now support LDAP (including Microsoft's Active -Directory), and there are a number of servers available. The most popular -implementation for Unix is from the University of Michigan; its -homepage is at http://www.umich.edu/~dirsvcs/ldap/.

- Information in an LDAP tree always comes in attribute=value pairs. -The following is an example of a Samba user entry:

- 

-uid=jbloggs, dc=samba, dc=org
-objectclass=sambaAccount
-uid=jbloggs
-cn=Joe Bloggs
-description=Samba User
-uidNumber=500
-gidNumber=500
-rid=2000
-grouprid=2001
-lmPassword=46E389809F8D55BB78A48108148AD508
-ntPassword=1944CCE1AD6F80D8AEC9FC5BE77696F4
-pwdLastSet=35C11F1B
-smbHome=\\samba1\jbloggs
-homeDrive=Z
-script=logon.bat
-profile=\\samba1\jbloggs\profile
-workstations=JOE
-
-

- Note that the top line is a special set of attributes called a -distinguished name which identifies the location of this entry beneath -the directory's root node. Recent Internet standards suggest the use of -domain-based naming using dc attributes (for instance, a microsoft.com -directory should have a root node of dc=microsoft, dc=com), although -this is not strictly necessary for isolated servers.

- There are a number of LDAP-related FAQ's on the internet, although -generally the best source of information is the documentation for the -individual servers.

-
- -

2: Why LDAP and Samba?

- Using an LDAP directory allows Samba to store user and group information -more reliably and flexibly than the current combination of smbpasswd, -smbgroup, groupdb and aliasdb with the Unix databases. If a need emerges -for extra user information to be stored, this can easily be added without -loss of backwards compatibility.

- In addition, the Samba LDAP schema is compatible with RFC2307, allowing -Unix password database information to be stored in the same entries. This -provides a single, consistent repository for both Unix and Windows user -information.

-
- -

3: Using LDAP with Samba

-

    -

  1. Install and configure an LDAP server if you do not already have -one. You should read your LDAP server's documentation and set up the -configuration file and access control as desired.

    -

  2. Build Samba (latest CVS is required) with:

    - 

    -	./configure --with-ldap
-	make clean; make install
-
    -

    -

  3. Add the following options to the global section of smb.conf as -required.

    -

      -
    • ldap suffix

      - This parameter specifies the node of the LDAP tree beneath which -Samba should store its information. This parameter MUST be provided -when using LDAP with Samba.

      - Default: none

      - Example: ldap suffix = "dc=mydomain, dc=org"

      -

    • ldap bind as

      - This parameter specifies the entity to bind to an LDAP directory as. -Usually it should be safe to use the LDAP root account; for larger -installations it may be preferable to restrict Samba's access.

      - Default: none (bind anonymously)

      - Example: ldap bind as = "uid=root, dc=mydomain, dc=org"

      -

    • ldap passwd file

      - This parameter specifies a file containing the password with which -Samba should bind to an LDAP server. For obvious security reasons -this file must be set to mode 700 or less.

      - Default: none (bind anonymously)

      - Example: ldap passwd file = /usr/local/samba/private/ldappasswd

      -

    • ldap server

      - This parameter specifies the DNS name of the LDAP server to use -when storing and retrieving information about Samba users and -groups.

      - Default: ldap server = localhost

      -

    • ldap port

      - This parameter specifies the TCP port number of the LDAP server.

      - Default: ldap port = 389

      -

    -

  4. You should then be able to use the normal smbpasswd(8) command for -account administration (or User Manager in the near future).

    -

-
- -

4: Using LDAP for Unix authentication

- The Samba LDAP code was designed to utilise RFC2307-compliant directory -entries if available. RFC2307 is a proposed standard for LDAP user -information which has been adopted by a number of vendors. Further -information is available at http://www.xedoc.com.au/~lukeh/ldap/.

- Of particular interest is Luke Howard's nameservice switch module -(nss_ldap) and PAM module (pam_ldap) implementing this standard, providing -LDAP-based password databases for Unix. If you are setting up a server to -provide integrated Unix/NT services than these are worth investigating.

-
- -

5: Compatibility with Active Directory

- The current implementation is not designed to be used with Microsoft -Active Directory, although compatibility may be added in the future.

- - diff --git a/docs/htmldocs/debug2html.1.html b/docs/htmldocs/debug2html.1.html deleted file mode 100644 index d0d6373a3d..0000000000 --- a/docs/htmldocs/debug2html.1.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -debug2html(1) - - - - - -

- -

debug2html(1)

-

Samba

-

29 Dec 1998

- - - - -


-

NAME

- debug2html - Samba DEBUG to HTML translation filter -


-

SYNOPSIS

- -


debug2html [input-file [output-file]] -


-

DESCRIPTION

- -


This program is part of the Samba suite. -


debug2html generates HTML files from Samba log files. Log files -produced by nmbd(8) or smbd(8) may then be viewed by a web -browser. The output conforms to the HTML 3.2 specification. -


The filenames specified on the command line are optional. If the -output-file is ommitted, output will go to stdout. If the input-file -is ommitted, debug2html will read from stdin. The filename "-" -can be used to indicate that input should be read from stdin. For -example: -


cat /usr/local/samba/var/log.nmb | debug2html - nmblog.html
-


-

VERSION

- -


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


-

SEE ALSO

- -


nmbd(8), smbd(8), -samba(7). -


-

AUTHOR

- -


The original Samba software and related utilities were created by -Andrew Tridgell samba-bugs@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-bugs@samba.org. -


debug2html was added by Chris Hertel. -


See samba(7) to find out how to get a full -list of contributors and details on how to submit bug reports, -comments etc. - - diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html deleted file mode 100644 index 6e5cf88866..0000000000 --- a/docs/htmldocs/rpcclient.1.html +++ /dev/null @@ -1,651 +0,0 @@ - - - - - -rpcclient (1) - - - - - -

- -

rpcclient (1)

-

Samba

-

23 Oct 1998

- - - - -


-

NAME

- rpcclient - utility to manage MSRPC resources on servers -


-

SYNOPSIS

- -


rpcclient -[password] --S servername -[-U [username][%][password]] -[-W domain] -[-l log basename] -[-d debuglevel] -[-O socket options] -[-i scope] -[-N] -[-n NetBIOS name] -[-h] -[-I dest IP] -[-E] -[-t terminal code] -[-c command string] -[-B IP addr] -[-s smb.conf] -[-m max protocol] -


-

DESCRIPTION

- -


This program is part of the Samba suite. -


rpcclient is a client that can 'talk' to an SMB/CIFS MSRPC server. -Operations include things like managing a SAM Database (users, groups -and aliases) in the same way as the Windows NT programs -User Manager for Domains and Server Manager for Domains; -managing a remote registry in the same way as the Windows NT programs -REGEDT32.EXE and REGEDIT.EXE; viewing a remote event log (same -as EVENTVWR.EXE) etc. -


Typical usage is like this:
-rpcclient -I 192.168.32.1 -S "*SMBSERVER" -U fred%secret -l log -
-


-

OPTIONS

- -


-


-

OPERATIONS

- -


Once the client is running, the user is presented with a prompt : -


smb:\> -


The prompt indicates that the client is ready and waiting to carry out -a user command. Each command is a single word, optionally followed by -parameters specific to that command. Command and parameters are -space-delimited unless these notes specifically state otherwise. All -commands are case-insensitive. Parameters to commands may or may not -be case sensitive, depending on the command. -


You can specify names (e.g registry keys; user or group names; -service names) which have spaces in them by quoting the -name with double quotes, for example "dRMON SmartAgent". -


Parameters shown in square brackets (e.g., "[parameter]") are -optional. If not given, the command will use suitable -defaults. Parameters shown in angle brackets (e.g., "<parameter>") are -required. -


Note that all commands operating on the server are actually performed -by issuing a request to the server. Thus the behavior may vary from -server to server, depending on how the server was implemented. -


The commands available are listed in groups relating to different services: -


-


-

NOTES

- -


Some servers are fussy about the case of supplied usernames, -passwords, share names (AKA service names) and machine names. If you -fail to connect try giving all parameters in uppercase. -


It is often necessary to use the -n option when connecting -to some types of servers. For example OS/2 LanManager insists on a valid -NetBIOS name being used, so you need to supply a valid name that would -be known to the server. -


rpcclient only works on servers that support MSRPC over SMB. This includes -all versions of Windows NT, including the ports to Unix such as AS/U and -AFPS. Support for MSRPC over SMB in other servers is currently rare and -patchy, for example Samba 2.0 only supports a limited set of MSRPC commands, -and some of those are not supported very well. -


-

ENVIRONMENT VARIABLES

- -


The variable USER may contain the username of the person using the -client. This information is used only if the protocol level is high -enough to support session-level passwords. -


The variable PASSWORD may contain the password of the person using -the client. This information is used only if the protocol level is -high enough to support session-level passwords. -


-

INSTALLATION

- -


The location of the client program is a matter for individual system -administrators. The following are thus suggestions only. -


It is recommended that the rpcclient software be installed in the -/usr/local/samba/bin or /usr/samba/bin directory, this directory -readable by all, writeable only by root. The client program itself -should be executable by all. The client should NOT be setuid or -setgid! -


The client log files should be put in a directory readable and -writeable only by the user. -


To test the client, you will need to know the name of a running -SMB/CIFS server. It is possible to run smbd (8) -an ordinary user - running that server as a daemon on a -user-accessible port (typically any port number over 1024) would -provide a suitable test server. -


-

DIAGNOSTICS

- -


Most diagnostics issued by the client are logged in a specified log -file. The log file name is specified at compile time, but may be -overridden on the command line. -


The number and nature of diagnostics available depends on the debug -level used by the client. If you have problems, set the debug level to -3 and peruse the log files. -


-

VERSION

- -


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


-

BUGS

- -


-


-

AUTHOR

- -


The original Samba software and related utilities were created by -Andrew Tridgell samba-bugs@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. This man page -was developed cut-and-paste style from the smbclient man page, by -Luke Kenneth Casson Leighton. -samba-bugs@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. -


- -- cgit