Attachment 2244 Details for Bug 4315 – svn diff with proposed fixes

[patch] svn diff with proposed fixes

TOSHARG-Passdb.xml.faw.2006122800.diff (text/plain), 3.24 KB, created by Felipe Augusto van de Wiel on 2006-12-28 15:28:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Felipe Augusto van de Wiel

Created: 2006-12-28 15:28:23 UTC

Size: 3.24 KB

patch

obsolete

>Index: TOSHARG-Passdb.xml
>===================================================================
>--- TOSHARG-Passdb.xml	(revision 1008)
>+++ TOSHARG-Passdb.xml	(working copy)
>@@ -758,7 +758,7 @@
> <indexterm><primary>trust accounts</primary></indexterm>
> 		The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
> 		Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
>-		them. A user account and a machine account are indistinquishable from each other, except that
>+		them. A user account and a machine account are indistinguishable from each other, except that
> 		the machine account ends in a $ character, as do trust accounts.
> 		</para>
> 
>@@ -1051,7 +1051,7 @@
> 					<entry><para>0</para></entry>
>                     </row>
>                     <row>
>-					<entry><para>Mimimum Password Length</para></entry>
>+					<entry><Para>Minimum Password Length</para></entry>
> 					<entry><para>min password length</para></entry>
> 					<entry><para>1 - 14 (Chars)</para></entry>
> 					<entry><para>0 - 4294967295 (Chars)</para></entry>
>@@ -1426,7 +1426,7 @@
> <indexterm><primary>trust account</primary></indexterm>
> <indexterm><primary>damaged data</primary></indexterm>
> 		The manual adjustment of user, machine (workstation or server) or an inter-domain trust
>-		account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
>+		account account flags should not be necessary under normal conditions of use of Samba. On the other hand,
> 		where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
> 		useful. The tool of choice by which such correction can be affected is the <command>pdbedit</command> utility.
> 		</para>
>@@ -1616,9 +1616,9 @@
> &rootprompt; pdbedit -P "maximum password age" -C 7776000
> account policy value for maximum password age was 4294967295
> account policy value for maximum password age is now 7776000
>-&rootprompt; pdbedit -P "minimum password age" -C 7
>+&rootprompt; pdbedit -P "minimum password age" -C 604800 
> account policy value for minimum password age was 0
>-account policy value for minimum password age is now 7
>+account policy value for minimum password age is now 604800
> &rootprompt; pdbedit -P "bad lockout attempt" -C 8
> account policy value for bad lockout attempt was 0
> account policy value for bad lockout attempt is now 8
>@@ -1744,7 +1744,7 @@
> 		<listitem><para>
> <indexterm><primary>lookups</primary></indexterm>
> 		The first problem is that all lookups must be performed sequentially. Given that
>-		there are approximately two lookups per domain logon (one during intial logon validation
>+		there are approximately two lookups per domain logon (one during initial logon validation
> 		and one for a session connection setup, such as when mapping a network drive or printer), this
> 		is a performance bottleneck for large sites. What is needed is an indexed approach
> 		such as that used in databases.
>@@ -2635,7 +2635,7 @@
> 		</sect3>
> 
> 		<sect3>
>-		<title>Using OpenLDAP Overlay for Password Syncronization</title>
>+		<title>Using OpenLDAP Overlay for Password Synchronization</title>
> 
> 		<para>
> 		Howard Chu has written a special overlay called <command>smbk5pwd</command>. This tool  modifies the

Actions: View

Attachments on bug 4315: 2244