[SCM] Samba Shared Repository - branch master updated

Andreas Schneider asn at samba.org
Wed May 10 17:58:02 UTC 2017


The branch, master has been updated
       via  cc7ae10 docs: Rename Samba3-Developers-Guide to Samba-Developers-Guide
       via  8e52229 s3-lib/idmap_cache: remove some dead prototypes
       via  84451e8 s4-lib/policy: remove some dead prototypes
       via  86c9a02 s4-libcli: remove some dead prototypes
       via  0a74793 s4-auth: remove some dead prototypes
       via  3a11a79 s4-rpc_server: remove some dead prototypes
       via  02b4275 s3-rpc_server: remove some dead prototypes
       via  7567a86 s3-proto: remove some dead prototypes
       via  36f8f8e s3-libsmb: remove some dead prototype
       via  af8946d s3-lib: remove some dead prototypes
       via  3c96b18 s3-winbindd: remove some dead prototypes
       via  24c4a6a s3-smbd: remove some dead prototypes
       via  8e32167 lib/krb5_samba: remove some dead prototypes
       via  7575f54 s3-passdb: remove some dead prototypes
       via  693716d s3-auth: remove some dead prototypes
      from  de01e11 smbd/smb2_ioctl: instruct VFS to ignore locks for dup extents

https://git.samba.org/?p=samba.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit cc7ae1098aea2ea8da7acaf0228286332744ca81
Author: Karolin Seeger <kseeger at samba.org>
Date:   Fri May 5 11:11:07 2017 +0200

    docs: Rename Samba3-Developers-Guide to Samba-Developers-Guide
    
    This guide is not obsolete but needs an update.
    
    Signed-off-by: Karolin Seeger <kseeger at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>
    
    Autobuild-User(master): Andreas Schneider <asn at cryptomilk.org>
    Autobuild-Date(master): Wed May 10 19:57:36 CEST 2017 on sn-devel-144

commit 8e52229fe84ed7f4d0c78d4eaf084bbd3ac0d3a0
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 10:05:59 2017 +0200

    s3-lib/idmap_cache: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 84451e8639b2e347e62f8858c96a9979b8177163
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 09:34:33 2017 +0200

    s4-lib/policy: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 86c9a0228dc31fce3bd733b5a20c476681a5b739
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 09:33:47 2017 +0200

    s4-libcli: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 0a74793f0ec84d2ec2928f2482e341275e799b2b
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 09:32:06 2017 +0200

    s4-auth: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 3a11a797a74eb10bf00e5b0566339a2e9cbcfbe8
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 09:28:53 2017 +0200

    s4-rpc_server: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 02b4275e6db4fce4a1eef2b8d32880be7edeff01
Author: Günther Deschner <gd at samba.org>
Date:   Wed May 10 09:28:40 2017 +0200

    s3-rpc_server: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 7567a86604b279ab8b4e371e3fe73abe7c7e3e68
Author: Günther Deschner <gd at samba.org>
Date:   Tue May 9 11:19:00 2017 +0200

    s3-proto: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 36f8f8e81b37db4d16af9b913fbb25e4453f9c16
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 18:14:29 2017 +0200

    s3-libsmb: remove some dead prototype
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit af8946df255aa49aba0b6871e391265dfb4255f5
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 18:12:56 2017 +0200

    s3-lib: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 3c96b18be32442af52842ace45db725cf3034ea0
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 18:11:28 2017 +0200

    s3-winbindd: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 24c4a6a5957ed79786c03ba44df91768c5321dec
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 18:08:02 2017 +0200

    s3-smbd: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 8e321676b9131ea6183d6c3b988c1fa6d00e75a4
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 16:26:31 2017 +0200

    lib/krb5_samba: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 7575f54a90e9eb3d7b52643c270dfa09d66e81aa
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 15:37:31 2017 +0200

    s3-passdb: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

commit 693716d7e6cd7144d7087731a20d424c2dc785ca
Author: Günther Deschner <gd at samba.org>
Date:   Fri May 5 15:21:03 2017 +0200

    s3-auth: remove some dead prototypes
    
    Guenther
    
    Signed-off-by: Guenther Deschner <gd at samba.org>
    Reviewed-by: Andreas Schneider <asn at samba.org>

-----------------------------------------------------------------------

Summary of changes:
 .../CodingSuggestions.xml                          |  14 +-
 .../Tracing.xml                                    |  12 +-
 .../architecture.xml                               |   8 +-
 .../cifsntdomain.xml                               |  14 +-
 .../contributing.xml                               |  66 ++++-----
 .../debug.xml                                      |   2 +-
 .../encryption.xml                                 | 160 ++++++++++-----------
 .../gencache.xml                                   |   0
 .../index.xml                                      |  18 +--
 .../internals.xml                                  |  50 +++----
 .../modules.xml                                    |  60 ++++----
 .../packagers.xml                                  |   2 +-
 .../parsing.xml                                    |   4 +-
 .../printing.xml                                   |  16 +--
 .../rpc_plugin.xml                                 |   6 +-
 .../unix-smb.xml                                   |  15 +-
 .../vfs.xml                                        |  96 ++++++-------
 .../wins.xml                                       |  20 +--
 docs-xml/htmldocs.html                             |   2 +-
 lib/krb5_wrap/krb5_samba.h                         |   2 -
 source3/auth/proto.h                               |   9 --
 source3/include/passdb.h                           |   5 -
 source3/include/proto.h                            |  11 --
 source3/lib/id_cache.h                             |   6 -
 source3/lib/idmap_cache.h                          |   1 -
 source3/libsmb/proto.h                             |   1 -
 source3/rpc_server/rpc_service_setup.h             |  24 ----
 source3/smbd/proto.h                               |   1 -
 source3/winbindd/winbindd_proto.h                  |  28 ----
 source4/auth/auth.h                                |   7 -
 source4/lib/policy/policy.h                        |   2 -
 source4/libcli/raw/libcliraw.h                     |   1 -
 source4/rpc_server/dcerpc_server.h                 |   2 -
 33 files changed, 282 insertions(+), 383 deletions(-)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/CodingSuggestions.xml (96%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/Tracing.xml (96%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/architecture.xml (98%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/cifsntdomain.xml (99%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/contributing.xml (76%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/debug.xml (99%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/encryption.xml (77%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/gencache.xml (100%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/index.xml (87%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/internals.xml (96%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/modules.xml (91%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/packagers.xml (94%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/parsing.xml (99%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/printing.xml (98%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/rpc_plugin.xml (95%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/unix-smb.xml (99%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/vfs.xml (96%)
 rename docs-xml/{Samba3-Developers-Guide => Samba-Developers-Guide}/wins.xml (91%)


Changeset truncated at 500 lines:

diff --git a/docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml b/docs-xml/Samba-Developers-Guide/CodingSuggestions.xml
similarity index 96%
rename from docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml
rename to docs-xml/Samba-Developers-Guide/CodingSuggestions.xml
index caf93d8..5e44d03 100644
--- a/docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml
+++ b/docs-xml/Samba-Developers-Guide/CodingSuggestions.xml
@@ -34,7 +34,7 @@ document will attempt to document a few of the more important coding
 practices used at this time on the Samba project.  The coding practices are
 expected to change slightly over time, and even to grow as more is learned
 about obscure portability considerations.  Two existing documents
-<filename>samba/source/internals.doc</filename> and 
+<filename>samba/source/internals.doc</filename> and
 <filename>samba/source/architecture.doc</filename> provide
 additional information.
 </para>
@@ -84,7 +84,7 @@ Here are some other suggestions:
 
 <listitem><para>
 	use d_printf instead of printf for display text
-	reason: enable auto-substitution of translated language text 
+	reason: enable auto-substitution of translated language text
 </para></listitem>
 
 <listitem><para>
@@ -115,7 +115,7 @@ Here are some other suggestions:
 <listitem><para>
 	when passing a va_list as an arg, or assigning one to another
 	please use the VA_COPY() macro
-	reason: on some platforms, va_list is a struct that must be 
+	reason: on some platforms, va_list is a struct that must be
 	initialized in each function...can SEGV if you don't.
 </para></listitem>
 
@@ -125,13 +125,13 @@ Here are some other suggestions:
 </para></listitem>
 
 <listitem><para>
-	don't explicitly include new header files in C files - new h files 
+	don't explicitly include new header files in C files - new h files
 	should be included by adding them once to includes.h
 	reason: consistency
 </para></listitem>
 
 <listitem><para>
-	don't explicitly extern functions (they are autogenerated by 
+	don't explicitly extern functions (they are autogenerated by
 	"make proto" into proto.h)
 	reason: consistency
 </para></listitem>
@@ -219,13 +219,13 @@ Here are some other suggestions:
 	for fragile, hand to maintain code. Instead, design an interface
 	and use tables containing function pointers to implement specific
 	functionality. This is particularly important for command
-	interpreters. 
+	interpreters.
 </para></listitem>
 
 <listitem><para>
 	Think carefully about what it will be like for someone else to add
 	to and maintain your code. If it would be hard for someone else to
-	maintain then do it another way. 
+	maintain then do it another way.
 </para></listitem>
 
 </orderedlist>
diff --git a/docs-xml/Samba3-Developers-Guide/Tracing.xml b/docs-xml/Samba-Developers-Guide/Tracing.xml
similarity index 96%
rename from docs-xml/Samba3-Developers-Guide/Tracing.xml
rename to docs-xml/Samba-Developers-Guide/Tracing.xml
index 3eaab63..23b46d5 100644
--- a/docs-xml/Samba3-Developers-Guide/Tracing.xml
+++ b/docs-xml/Samba-Developers-Guide/Tracing.xml
@@ -29,14 +29,14 @@ that they nearly all come with a system trace utility that allows you
 to monitor all system calls that a program is making. This is
 extremely using for debugging and also helps when trying to work out
 why something is slower than you expect. You can use system tracing
-without any special compilation options. 
+without any special compilation options.
 </para>
 
 <para>
 The system trace utility is called different things on different
 systems. On Linux systems its called strace. Under SunOS 4 its called
 trace. Under SVR4 style systems (including solaris) its called
-truss. Under many BSD systems its called ktrace. 
+truss. Under many BSD systems its called ktrace.
 </para>
 
 <para>
@@ -52,7 +52,7 @@ Next, try using strace on some simple commands. For example, <command>strace
 ls</command> or <command>strace echo hello</command>.
 </para>
 
-<para> 
+<para>
 You'll notice that it produces a LOT of output. It is showing you the
 arguments to every system call that the program makes and the
 result. Very little happens in a program without a system call so you
@@ -98,7 +98,7 @@ forks. This is great for finding printing problems caused by the
 <para>
 Once you are attached you then can do whatever it is on the client
 that is causing problems and you will capture all the system calls
-that smbd makes. 
+that smbd makes.
 </para>
 
 <para>
@@ -123,8 +123,8 @@ causes printing to fail with Samba:
 </programlisting></para>
 
 <para>
-The process is trying to first open <filename>/dev/null</filename> read-write 
-then read-only. Both fail. This means <filename>/dev/null</filename> has 
+The process is trying to first open <filename>/dev/null</filename> read-write
+then read-only. Both fail. This means <filename>/dev/null</filename> has
 incorrect permissions.
 </para>
 
diff --git a/docs-xml/Samba3-Developers-Guide/architecture.xml b/docs-xml/Samba-Developers-Guide/architecture.xml
similarity index 98%
rename from docs-xml/Samba3-Developers-Guide/architecture.xml
rename to docs-xml/Samba-Developers-Guide/architecture.xml
index bb0f299..1ad6993 100644
--- a/docs-xml/Samba3-Developers-Guide/architecture.xml
+++ b/docs-xml/Samba-Developers-Guide/architecture.xml
@@ -18,7 +18,7 @@ This document gives a general overview of how Samba works
 internally. The Samba Team has tried to come up with a model which is
 the best possible compromise between elegance, portability, security
 and the constraints imposed by the very messy SMB and CIFS
-protocol. 
+protocol.
 </para>
 
 <para>
@@ -45,7 +45,7 @@ It also tries to answer some of the frequently asked questions such as:
 <para>
 People sometimes tout threads as a uniformly good thing. They are very
 nice in their place but are quite inappropriate for smbd. nmbd is
-another matter, and multi-threading it would be very nice. 
+another matter, and multi-threading it would be very nice.
 </para>
 
 <para>
@@ -90,7 +90,7 @@ A few problems that would arise from a threaded smbd are:
 	many of the system calls we make are blocking. Non-blocking
 	equivalents of many calls are either not available or are awkward (and
 	slow) to use. So while we block in one thread all clients are
-	waiting. Imagine if one share is a slow NFS filesystem and the others 
+	waiting. Imagine if one share is a slow NFS filesystem and the others
 	are fast, we will end up slowing all clients to the speed of NFS.
 </para></listitem>
 
@@ -179,7 +179,7 @@ wire. It's a nice format that is very amenable to processing but still
 keeps the idea of a distinct packet. See "struct packet_struct" in
 nameserv.h.  It has all the detail but none of the on-the-wire
 mess. This makes it ideal for using in disk or memory-based databases
-for browsing and WINS support. 
+for browsing and WINS support.
 </para>
 
 </sect1>
diff --git a/docs-xml/Samba3-Developers-Guide/cifsntdomain.xml b/docs-xml/Samba-Developers-Guide/cifsntdomain.xml
similarity index 99%
rename from docs-xml/Samba3-Developers-Guide/cifsntdomain.xml
rename to docs-xml/Samba-Developers-Guide/cifsntdomain.xml
index 8467a6f..a302fb1 100644
--- a/docs-xml/Samba3-Developers-Guide/cifsntdomain.xml
+++ b/docs-xml/Samba-Developers-Guide/cifsntdomain.xml
@@ -48,7 +48,7 @@ instructive than this document.
 </para>
 
 <para>
-Also needed, to fully implement NT Domain Login Services, is the 
+Also needed, to fully implement NT Domain Login Services, is the
 document describing the cryptographic part of the NT authentication.
 This document is available from comp.protocols.smb; from the ntsecurity.net
 digest and from the samba digest, amongst other sources.
@@ -79,7 +79,7 @@ achieved by setting the following REG_SZ registry key to 0x1ffffff:
 <para><filename>HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters</filename></para>
 
 <para><emphasis>Incorrect direct editing of the registry can cause your
-machine to fail. Then again, so can incorrect implementation of this 
+machine to fail. Then again, so can incorrect implementation of this
 protocol. See "Liability:" above.</emphasis></para>
 
 <para>
@@ -103,11 +103,11 @@ include, but are not limited to:
 <listitem><para>The exact meaning/definition of various magic constants or enumerations.</para></listitem>
 
 <listitem><para>The reply error code and use of that error code when a
-workstation becomes a member of a domain (to be described later).  
-Failure to return this error code will make the workstation report 
+workstation becomes a member of a domain (to be described later).
+Failure to return this error code will make the workstation report
 that it is already a member of the domain.</para></listitem>
 
-<listitem><para>the cryptographic side of the NetrServerPasswordSet command, 
+<listitem><para>the cryptographic side of the NetrServerPasswordSet command,
 which would allow the workstation to change its password.  This password is
 used to generate the long-term session key.  [It is possible to reject this
 command, and keep the default workstation password].</para></listitem>
@@ -129,7 +129,7 @@ command, and keep the default workstation password].</para></listitem>
 <sect2>
 <title>Credits</title>
 
-<simplelist> 
+<simplelist>
 <member>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</member>
 <member>Duncan Stansfield: low-level analysis of MSRPC Pipes.</member>
 <member>Linus Nordberg: producing c-code from Paul's crypto spec.</member>
@@ -1226,7 +1226,7 @@ appears a third time after the last sub-structure.
 <title>MSRPC Pipes</title>
 
 <para>
-The MSRPC is conducted over an SMB Transact Pipe with a name of 
+The MSRPC is conducted over an SMB Transact Pipe with a name of
 <filename>\PIPE\</filename>.  You must first obtain a 16 bit file handle, by
 sending a SMBopenX with the pipe name <filename>\PIPE\srvsvc</filename> for
 example.  You can then perform an SMB Trans,
diff --git a/docs-xml/Samba3-Developers-Guide/contributing.xml b/docs-xml/Samba-Developers-Guide/contributing.xml
similarity index 76%
rename from docs-xml/Samba3-Developers-Guide/contributing.xml
rename to docs-xml/Samba-Developers-Guide/contributing.xml
index 61612d7..af21b6e 100644
--- a/docs-xml/Samba3-Developers-Guide/contributing.xml
+++ b/docs-xml/Samba-Developers-Guide/contributing.xml
@@ -8,8 +8,8 @@
 
 <title>Contributing code</title>
 
-<para>Here are a few tips and notes that might be useful if you are 
-	interested in modifying samba source code and getting it into 
+<para>Here are a few tips and notes that might be useful if you are
+	interested in modifying samba source code and getting it into
 	samba's main branch.</para>
 
 <variablelist>
@@ -17,8 +17,8 @@
 		<term>Retrieving the source</term>
 
 		<listitem>
-		<para>In order to contribute code to samba, make sure you have the 
-			latest source. Retrieving the samba source code from CVS is 
+		<para>In order to contribute code to samba, make sure you have the
+			latest source. Retrieving the samba source code from CVS is
 			documented in the appendix of the Samba HOWTO Collection.
 		</para>
 		</listitem>
@@ -27,15 +27,15 @@
 	<varlistentry>
 		<term>Discuss large modifications with team members</term>
 		<listitem>
-		<para>Please discuss large modifications you are going to make 
-		with members of the samba team. Some parts of the samba code 
-		have one or more 'owners' - samba developers who wrote most 
-		of the code and maintain it. 
+		<para>Please discuss large modifications you are going to make
+		with members of the samba team. Some parts of the samba code
+		have one or more 'owners' - samba developers who wrote most
+		of the code and maintain it.
 		</para>
 
-		<para>This way you can avoid spending your time and effort on 
-		something that is not going to make it into the main samba branch 
-		because someone else was working on the same thing or because your 
+		<para>This way you can avoid spending your time and effort on
+		something that is not going to make it into the main samba branch
+		because someone else was working on the same thing or because your
 		implementation is not the correct one.
 		</para>
 		</listitem>
@@ -44,13 +44,13 @@
 	<varlistentry>
 		<term>Patch format</term>
 		<listitem>
-		<para>Patches to the samba tree should be in unified diff format, 
-			e.g. files generated by <userinput>diff -u</userinput>. 
+		<para>Patches to the samba tree should be in unified diff format,
+			e.g. files generated by <userinput>diff -u</userinput>.
 		</para>
 
-		<para>If you are modifying a copy of samba you retrieved from CVS, 
-		you can easily generate a diff file of these changes by running 
-		<userinput>cvs diff -u</userinput>.</para>			
+		<para>If you are modifying a copy of samba you retrieved from CVS,
+		you can easily generate a diff file of these changes by running
+		<userinput>cvs diff -u</userinput>.</para>
 		</listitem>
 	</varlistentry>
 
@@ -59,17 +59,17 @@
 		<listitem><para>
 		<itemizedlist>
 		<listitem><para>Don't simply copy code from other places and modify it until it
-		works. Code needs to be clean and logical. Duplicate 
+		works. Code needs to be clean and logical. Duplicate
 		code is to be avoided.</para></listitem>
-		<listitem><para>Test your patch. It might take a while before one of us looks 
-		at your patch so it will take longer before your patch when your patch 
+		<listitem><para>Test your patch. It might take a while before one of us looks
+		at your patch so it will take longer before your patch when your patch
 		needs to go thru the review cycle again.</para></listitem>
-		<listitem><para>Don't put separate patches in one large diff file. This makes 
-		it harder to read, understand and test the patch. You might 
-		also risk not getting a good patch committed because you mixed it 
+		<listitem><para>Don't put separate patches in one large diff file. This makes
+		it harder to read, understand and test the patch. You might
+		also risk not getting a good patch committed because you mixed it
 		with one that had issues. </para></listitem>
-		<listitem><para>Make sure your patch complies to the samba coding style as 
- 		suggested in the coding-suggestions chapter. </para></listitem>
+		<listitem><para>Make sure your patch complies to the samba coding style as
+		suggested in the coding-suggestions chapter. </para></listitem>
 			</itemizedlist>
 		</para>
 		</listitem>
@@ -79,7 +79,7 @@
 		<term>Sending in bugfixes</term>
 		<listitem>
 		<para>Bugfixes to bugs in samba should be submitted to samba's
-		<ulink url="https://bugzilla.samba.org/">bugzilla system</ulink>, 
+		<ulink url="https://bugzilla.samba.org/">bugzilla system</ulink>,
 		along with a description of the bug.
 		</para>
 		</listitem>
@@ -88,12 +88,12 @@
 	<varlistentry>
 		<term>Sending in feature patches</term>
 		<listitem>
-		<para>Send feature patches along with a description of what the 
-		patch is supposed to do to the 
+		<para>Send feature patches along with a description of what the
+		patch is supposed to do to the
 		<ulink url="mailto:samba-technical at lists.samba.org">Samba-technical mailinglist</ulink> and possibly to a samba team member who is (one of the) 'owners'
-		of the code you made modifications to. We are all busy people 
-		so everybody tends to 'let one of the others handle it'. If nobody 
-		responded to your patch for a week, try to send it again until you 
+		of the code you made modifications to. We are all busy people
+		so everybody tends to 'let one of the others handle it'. If nobody
+		responded to your patch for a week, try to send it again until you
 		get a response from one of us.
 		</para></listitem>
 	</varlistentry>
@@ -101,9 +101,9 @@
 	<varlistentry>
 		<term>Feedback on your patch</term>
 		<listitem>
-		<para>One of the team members will look at your patch and either 
-		commit your patch or give comments why he won't apply it. In the 
-		latter case you can fix your patch and re-send it until 
+		<para>One of the team members will look at your patch and either
+		commit your patch or give comments why he won't apply it. In the
+		latter case you can fix your patch and re-send it until
 		your patch is approved.</para>
 		</listitem>
 	</varlistentry>
diff --git a/docs-xml/Samba3-Developers-Guide/debug.xml b/docs-xml/Samba-Developers-Guide/debug.xml
similarity index 99%
rename from docs-xml/Samba3-Developers-Guide/debug.xml
rename to docs-xml/Samba-Developers-Guide/debug.xml
index a55face..50a363c 100644
--- a/docs-xml/Samba3-Developers-Guide/debug.xml
+++ b/docs-xml/Samba-Developers-Guide/debug.xml
@@ -287,7 +287,7 @@ input is printed into a buffer using the vslprintf() function,
 and then passed to format_debug_text().
 
 If you use DEBUGLVL() you will probably print the body of the
-message using dbgtext(). 
+message using dbgtext().
 </para>
 </sect2>
 
diff --git a/docs-xml/Samba3-Developers-Guide/encryption.xml b/docs-xml/Samba-Developers-Guide/encryption.xml
similarity index 77%
rename from docs-xml/Samba3-Developers-Guide/encryption.xml
rename to docs-xml/Samba-Developers-Guide/encryption.xml
index a4405a9..cba9490 100644
--- a/docs-xml/Samba3-Developers-Guide/encryption.xml
+++ b/docs-xml/Samba-Developers-Guide/encryption.xml
@@ -16,92 +16,92 @@
 
 	<pubdate>19 Apr 1999</pubdate>
 </chapterinfo>
-	
+
 <title>LanMan and NT Password Encryption</title>
 
 <sect1>
 	<title>Introduction</title>
-	
-	<para>With the development of LanManager and Windows NT 
-	compatible password encryption for Samba, it is now able 
-	to validate user connections in exactly the same way as 
+
+	<para>With the development of LanManager and Windows NT
+	compatible password encryption for Samba, it is now able
+	to validate user connections in exactly the same way as
 	a LanManager or Windows NT server.</para>
 
-	<para>This document describes how the SMB password encryption 
-	algorithm works and what issues there are in choosing whether 
-	you want to use it. You should read it carefully, especially 
+	<para>This document describes how the SMB password encryption
+	algorithm works and what issues there are in choosing whether
+	you want to use it. You should read it carefully, especially
 	the part about security and the "PROS and CONS" section.</para>
-	
+
 </sect1>
 
 <sect1>
 	<title>How does it work?</title>
 
-	<para>LanManager encryption is somewhat similar to UNIX 
-	password encryption. The server uses a file containing a 
-	hashed value of a user's password.  This is created by taking 
-	the user's plaintext password, capitalising it, and either 
-	truncating to 14 bytes or padding to 14 bytes with null bytes. 
-	This 14 byte value is used as two 56 bit DES keys to encrypt 
-	a 'magic' eight byte value, forming a 16 byte value which is 
-	stored by the server and client. Let this value be known as 
+	<para>LanManager encryption is somewhat similar to UNIX
+	password encryption. The server uses a file containing a
+	hashed value of a user's password.  This is created by taking
+	the user's plaintext password, capitalising it, and either
+	truncating to 14 bytes or padding to 14 bytes with null bytes.
+	This 14 byte value is used as two 56 bit DES keys to encrypt
+	a 'magic' eight byte value, forming a 16 byte value which is
+	stored by the server and client. Let this value be known as
 	the "hashed password".</para>
-	
-	<para>Windows NT encryption is a higher quality mechanism, 
-	consisting of doing an MD4 hash on a Unicode version of the user's 
-	password. This also produces a 16 byte hash value that is 
+
+	<para>Windows NT encryption is a higher quality mechanism,
+	consisting of doing an MD4 hash on a Unicode version of the user's
+	password. This also produces a 16 byte hash value that is
 	non-reversible.</para>
 
-	<para>When a client (LanManager, Windows for WorkGroups, Windows 
-	95 or Windows NT) wishes to mount a Samba drive (or use a Samba 
-	resource), it first requests a connection and negotiates the 
-	protocol that the client and server will use. In the reply to this 
-	request the Samba server generates and appends an 8 byte, random 
-	value - this is stored in the Samba server after the reply is sent 
-	and is known as the "challenge".  The challenge is different for 
+	<para>When a client (LanManager, Windows for WorkGroups, Windows
+	95 or Windows NT) wishes to mount a Samba drive (or use a Samba
+	resource), it first requests a connection and negotiates the
+	protocol that the client and server will use. In the reply to this
+	request the Samba server generates and appends an 8 byte, random
+	value - this is stored in the Samba server after the reply is sent
+	and is known as the "challenge".  The challenge is different for
 	every client connection.</para>
 
-	<para>The client then uses the hashed password (16 byte values 
-	described above), appended with 5 null bytes, as three 56 bit 
-	DES keys, each of which is used to encrypt the challenge 8 byte 
+	<para>The client then uses the hashed password (16 byte values
+	described above), appended with 5 null bytes, as three 56 bit
+	DES keys, each of which is used to encrypt the challenge 8 byte
 	value, forming a 24 byte value known as the "response".</para>
 
-	<para>In the SMB call SMBsessionsetupX (when user level security 
-	is selected) or the call SMBtconX (when share level security is 
-	selected), the 24 byte response is returned by the client to the 
-	Samba server.  For Windows NT protocol levels the above calculation 
-	is done on both hashes of the user's password and both responses are 
+	<para>In the SMB call SMBsessionsetupX (when user level security
+	is selected) or the call SMBtconX (when share level security is
+	selected), the 24 byte response is returned by the client to the
+	Samba server.  For Windows NT protocol levels the above calculation
+	is done on both hashes of the user's password and both responses are
 	returned in the SMB call, giving two 24 byte values.</para>
 
-	<para>The Samba server then reproduces the above calculation, using 
-	its own stored value of the 16 byte hashed password (read from the 
-	<filename>smbpasswd</filename> file - described later) and the challenge 
-	value that it kept from the negotiate protocol reply. It then checks 
-	to see if the 24 byte value it calculates matches the 24 byte value 
+	<para>The Samba server then reproduces the above calculation, using
+	its own stored value of the 16 byte hashed password (read from the
+	<filename>smbpasswd</filename> file - described later) and the challenge
+	value that it kept from the negotiate protocol reply. It then checks
+	to see if the 24 byte value it calculates matches the 24 byte value
 	returned to it from the client.</para>
 
-	<para>If these values match exactly, then the client knew the 
-	correct password (or the 16 byte hashed value - see security note 
-	below) and is thus allowed access. If not, then the client did not 
+	<para>If these values match exactly, then the client knew the
+	correct password (or the 16 byte hashed value - see security note
+	below) and is thus allowed access. If not, then the client did not
 	know the correct password and is denied access.</para>
 
-	<para>Note that the Samba server never knows or stores the cleartext 
-	of the user's password - just the 16 byte hashed values derived from 
-	it. Also note that the cleartext password or 16 byte hashed values 


-- 
Samba Shared Repository



More information about the samba-cvs mailing list