From 0c7e28f655efb3abe297aa15da7f0d487cb865cc Mon Sep 17 00:00:00 2001 From: cvs2svn Import User Date: Tue, 18 May 1999 17:49:52 +0000 Subject: [PATCH] This commit was manufactured by cvs2svn to create tag 'release-2-0-4a'. --- docs/htmldocs/lmhosts.5.html | 94 --------------------------------------- docs/textdocs/NT-Guest-Access.txt | 46 ------------------- 2 files changed, 140 deletions(-) delete mode 100644 docs/htmldocs/lmhosts.5.html delete mode 100644 docs/textdocs/NT-Guest-Access.txt diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html deleted file mode 100644 index ece68eb5114..00000000000 --- a/docs/htmldocs/lmhosts.5.html +++ /dev/null @@ -1,94 +0,0 @@ - - - - - -lmhosts (5) - - - - - -
- -

lmhosts (5)

-

Samba

-

23 Oct 1998

- - - - -


-

NAME

- lmhosts - The Samba NetBIOS hosts file -


-

SYNOPSIS

- -


lmhosts is the Samba NetBIOS name to IP address mapping file. -


-

DESCRIPTION

- -


This file is part of the Samba suite. -


lmhosts is the Samba NetBIOS name to IP address mapping file. It -is very similar to the /etc/hosts file format, except that the -hostname component must correspond to the NetBIOS naming format. -


-

FILE FORMAT

- -


It is an ASCII file containing one line for NetBIOS name. The two -fields on each line are separated from each other by white space. Any -entry beginning with # is ignored. Each line in the lmhosts file -contains the following information : -


-


An example follows : -


#
-# Sample Samba lmhosts file.
-#
-192.9.200.1 TESTPC
-192.9.200.20 NTSERVER#20
-192.9.200.21 SAMBASERVER
-


Contains three IP to NetBIOS name mappings. The first and third will -be returned for any queries for the names "TESTPC" and -"SAMBASERVER" respectively, whatever the type component of the -NetBIOS name requested. -


The second mapping will be returned only when the "0x20" name type -for a name "NTSERVER" is queried. Any other name type will not be -resolved. -


The default location of the lmhosts file is in the same directory -as the smb.conf file. -


-

VERSION

- -


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


-

SEE ALSO

- -


smb.conf (5), -smbclient (1), -smbpasswd (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. -


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/textdocs/NT-Guest-Access.txt b/docs/textdocs/NT-Guest-Access.txt deleted file mode 100644 index 892a535fcf3..00000000000 --- a/docs/textdocs/NT-Guest-Access.txt +++ /dev/null @@ -1,46 +0,0 @@ -!== -!== NT-Guest-Access.txt for Samba release 2.0.4 18 May 1999 -!== -> Hi folks ... I don't know if you have seen this, have corrected this yet -> or it is my configuration. -> I am using our company PDC for passwd authentication and it works OK -> except for one snag. -> The authentication process between the our Samba server & the PDC always -> includes one unsuccessful pass thru attempt. -> This initial pass thru validation has an incorrect user password -> (1F1F1F1F......). A SMB reject from the PDC forces the Samba Svr to -> immediately send a second validation with the correct -> encrypted Bell Master Domain user password. -> It would be nice to get rid of the first bad validation attempt. - -What you are seeing is being done deliberately. - -The problem is that some versions of MS Windows NT have a bug when -used as a password server when Samba is set up to use "security=server" -(Note that this is *NOT* a problem when using "security=domain"). - -The NT server accepts a user logon request with a bad password as -a "guest" login attempt, and logs the user on as the guest user. - -The bug is that the NT server doesn't tell the Samba server -that this is what it has done (it doesn't set the guest bit -that is designed for this use in the protocol). Thus the -Samba server cannot tell if a user entered a bad password -and was logged on as guest, or entered a correct user name -and password and was logged on as the correct user. - -The severity of this bug may be imagined if a user attempts -to access the Samba server as user "root" with a bad password, -and the Samba server trusted the NT server to authenticate -this..... - -Thus, Samba performs a logon request with a deliberately -bad password and checks to see if that request succeeded. -If it did, then the NT server suffers from the bug and cannot -be used for "security=server" authentication. If it fails -then we know this server is correct. - -It is this first deliberate invalid connection request that -people are seeing in the NT event log, but currently there -seems no way around this so long as there are NT servers -out there that have this bug. -- 2.11.4.GIT