summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorcvs2svn Import User <samba-bugs@samba.org>1999-05-18 17:49:52 +0000
committercvs2svn Import User <samba-bugs@samba.org>1999-05-18 17:49:52 +0000
commit0c7e28f655efb3abe297aa15da7f0d487cb865cc (patch)
tree5513e46934678de19b6f2c034daec498c026adb4
parent5122ac9c3a76493169c18b5970b852e368f97591 (diff)
downloadsamba-2.0.4a.tar.gz
samba-2.0.4a.tar.xz
samba-2.0.4a.zip
This commit was manufactured by cvs2svn to create tagsamba-2.0.4a
'release-2-0-4a'.
-rw-r--r--docs/htmldocs/lmhosts.5.html94
-rw-r--r--docs/textdocs/NT-Guest-Access.txt46
2 files changed, 0 insertions, 140 deletions
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 @@
-
-
-
-
-
-<html><head><title>lmhosts (5)</title>
-
-<link rev="made" href="mailto:samba-bugs@samba.org">
-</head>
-<body>
-
-<hr>
-
-<h1>lmhosts (5)</h1>
-<h2>Samba</h2>
-<h2>23 Oct 1998</h2>
-
-
-
-
-<p><br><a name="NAME"></a>
-<h2>NAME</h2>
- lmhosts - The Samba NetBIOS hosts file
-<p><br><a name="SYNOPSIS"></a>
-<h2>SYNOPSIS</h2>
-
-<p><br>lmhosts is the <strong>Samba</strong> NetBIOS name to IP address mapping file.
-<p><br><a name="DESCRIPTION"></a>
-<h2>DESCRIPTION</h2>
-
-<p><br>This file is part of the <strong>Samba</strong> suite.
-<p><br><strong>lmhosts</strong> is the <strong>Samba</strong> NetBIOS name to IP address mapping file. It
-is very similar to the <strong>/etc/hosts</strong> file format, except that the
-hostname component must correspond to the NetBIOS naming format.
-<p><br><a name="FILEFORMAT"></a>
-<h2>FILE FORMAT</h2>
-
-<p><br>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 :
-<p><br><ul>
-<p><br><li > <strong>IP Address</strong> - in dotted decimal format.
-<p><br><li > <strong>NetBIOS Name</strong> - This name format is a maximum fifteen
-character host name, with an optional trailing <code>'#'</code> character
-followed by the NetBIOS name type as two hexadecimal digits.
-<p><br>If the trailing <code>'#'</code> is omitted then the given IP address will be
-returned for all names that match the given name, whatever the NetBIOS
-name type in the lookup.
-<p><br></ul>
-<p><br>An example follows :
-<p><br># <br>
-# Sample Samba lmhosts file. <br>
-# <br>
-192.9.200.1 TESTPC <br>
-192.9.200.20 NTSERVER#20 <br>
-192.9.200.21 SAMBASERVER <br>
-<p><br>Contains three IP to NetBIOS name mappings. The first and third will
-be returned for any queries for the names <code>"TESTPC"</code> and
-<code>"SAMBASERVER"</code> respectively, whatever the type component of the
-NetBIOS name requested.
-<p><br>The second mapping will be returned only when the <code>"0x20"</code> name type
-for a name <code>"NTSERVER"</code> is queried. Any other name type will not be
-resolved.
-<p><br>The default location of the <strong>lmhosts</strong> file is in the same directory
-as the <a href="smb.conf.html"><strong>smb.conf</strong></a> file.
-<p><br><a name="VERSION"></a>
-<h2>VERSION</h2>
-
-<p><br>This man page is correct for version 2.0 of the Samba suite.
-<p><br><a name="SEEALSO"></a>
-<h2>SEE ALSO</h2>
-
-<p><br><a href="smb.conf.5.html#nameresolveorder"><strong>smb.conf (5)</strong></a>,
-<a href="smbclient.1.html#minusR"><strong>smbclient (1)</strong></a>,
-<a href="smbpasswd.8.html#minusR"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba (7)</strong></a>.
-<p><br><a name="AUTHOR"></a>
-<h2>AUTHOR</h2>
-
-<p><br>The original Samba software and related utilities were created by
-Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
-by the Samba Team as an Open Source project similar to the way the
-Linux kernel is developed.
-<p><br>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
-<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
-and updated for the Samba2.0 release by Jeremy Allison.
-<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
-<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
-list of contributors and details on how to submit bug reports,
-comments etc.
-</body>
-</html>
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.