svn commit: lorikeet r108 - in trunk/samba4-ad-thesis: .

[abartlet at samba.org]

Author: abartlet
Date: 2004-10-27 10:32:14 +0000 (Wed, 27 Oct 2004)
New Revision: 108

WebSVN: http://websvn.samba.org/websvn/changeset.php?rep=lorikeet&path=/trunk/samba4-ad-thesis&rev=108&nolog=1

Log:
And the fixes keep flowing in!  (All to appear in the acknowlegements page)

This lot from Jelmer Vernooij <jelmer at vernstok.nl>

Andrew Bartlett


Modified:
   trunk/samba4-ad-thesis/chapters.lyx


Changeset:
Modified: trunk/samba4-ad-thesis/chapters.lyx
===================================================================
--- trunk/samba4-ad-thesis/chapters.lyx	2004-10-27 10:22:29 UTC (rev 107)
+++ trunk/samba4-ad-thesis/chapters.lyx	2004-10-27 10:32:14 UTC (rev 108)
@@ -52,9 +52,9 @@
 
 , and forms the culmination of over 3 years personal effort as a member
  of that team.
- In researching the this thesis, I have been working on Samba4 since May
- 2004, and developed the authentication and GENSEC security subsystems (describe
-d in Section 
+ In researching this thesis, I have been working on Samba4 since May 2004,
+ and developed the authentication and GENSEC security subsystems (described
+ in Section 
 \begin_inset LatexCommand \ref{sec:GENSEC}
 
 \end_inset 
@@ -62,7 +62,7 @@
 ) as well as bringing some of my previous work into the Samba4 framework.
 \layout Standard
 
-This thesis contributes solid documentary basis for the work going forward,
+This thesis contributes a solid documentary basis for the work going forward,
  as well as specific forward development in the Kerberos area.
  
 \layout Section
@@ -158,9 +158,8 @@
  Windows 2003) architecture, this created an `all or nothing' problem.
 \layout Standard
 
-The Samba Team, lead by Dr.
- Tridgell, decided to remedy this problem in Samba4 by simply implementing
- the missing components.
+The Samba Team, lead by Dr Tridgell, decided to remedy this problem in Samba4
+ by simply implementing the missing components.
 \layout Section
 
 Kerberos
@@ -285,13 +284,13 @@
  This information is often organised into a hierarchy.
 \layout Standard
 
-The predominant directory access technology in use today is LDAP 
+The predominant directory access technology in use today is LDAP
 \begin_inset LatexCommand \citep{whatisldap,rfc2251}
 
 \end_inset 
 
-, a descendant of the X.500 directory standard from the ITU (and part of
- the full OSI networking stack)
+, a descendant of the X.500 directory standard from the International Telecommuni
+cation Union (ITU), and a component of the full OSI networking stack.
 \begin_inset LatexCommand \citep{X.500-LDAP,Understand-X.500}
 
 \end_inset 
@@ -332,11 +331,11 @@
  for the benefit of others much more than Microsoft's own clients.
  The technology Microsoft uses for client-server communication is remote
   procedure calls (RPC).
- The use of RPCs in Windows networking has grown  significantly since NT4.
+ The use of RPCs in Windows networking has grown significantly since NT4.
 \layout Standard
 
 These calls are not documented, even though the basic transport for them
- is DCE/RPC, for which  documents and a reference implementation are available
+ is DCE/RPC, for which documents and a reference implementation are available
  from The Open Group
 \begin_inset LatexCommand \citep{opengroupdce}
 
@@ -348,7 +347,7 @@
 \layout Standard
 
 Much of the challenge of Samba4 is the continued task of `network protocol
- analysis,' the art of determining the operation of a proprietary network
+ analysis', the art of determining the operation of a proprietary network
  protocol by examining network operations
 \begin_inset LatexCommand \citep{tridge-net-analysis}
 
@@ -580,7 +579,7 @@
 
 
 \family typewriter 
-ncacn_ip_udp
+ncadg_ip_udp
 \family default 
  DCE-RPC over UDP/IP
 \layout List
@@ -1769,7 +1768,7 @@
 Purpose
 \layout Standard
 
-The purpose of the `domain join' it to securely setup a password (shared
+The purpose of the `domain join' is to securely setup a password (shared
  secret) between the workstation (or member server) and the domain controllers,
  so it may use the NETLOGON mechanism described in 
 \begin_inset LatexCommand \ref{sub:NETLOGON}
@@ -2474,7 +2473,7 @@
 \layout Standard
 
 Standard in the sense of being TCP based (not UDP, as CLDAP is) and being
- largely conferment with the LDAPv3 specifications
+ largely conformant with the LDAPv3 specifications
 \begin_inset LatexCommand \citep{rfc2251}
 
 \end_inset 
@@ -3363,7 +3362,7 @@
 Kerberos in CIFS
 \layout Standard
 
-Adding correct Kerberos (and SPENGO) support into CIFS was the primary challenge
+Adding correct Kerberos (and SPNEGO) support into CIFS was the primary challenge
  in the Samba4 code-base, and in this area the project was very much a success.
  In this case, the keytab was manually exported from Heimdal, and the WinXP
  client successfully obtained a ticket, and used that ticket to log into
@@ -3400,9 +3399,9 @@
  domain.
  It turns out that the client clues in on Kerberos in the meantime, and
  proceeds to make a sucessful Kerberos connection to the Samba4 server,
- using the machine account! Unfortunetly, other issues with current Samba4
- prevent the login from proceeding, but these appear unreleated to the Kerberos
- work (it occours with Kerberos compleatly disabled), and is rather an unrelated
+ using the machine account! Unfortunately, other issues with current Samba4
+ prevent the login from proceeding, but these appear unrelated to the Kerberos
+ work (it occurs with Kerberos completely disabled), and is rather an unrelated
  regression.
 \layout Section