svn commit: lorikeet r107 - in trunk/samba4-ad-thesis: .
abartlet at samba.org
abartlet at samba.org
Wed Oct 27 10:22:30 GMT 2004
Date: 2004-10-27 10:22:29 +0000 (Wed, 27 Oct 2004)
New Revision: 107
More clarifications, spellcheck.
--- trunk/samba4-ad-thesis/chapters.lyx 2004-10-26 22:18:56 UTC (rev 106)
+++ trunk/samba4-ad-thesis/chapters.lyx 2004-10-27 10:22:29 UTC (rev 107)
@@ -212,7 +212,8 @@
More than had been done before
-The biggest change in Samba4 is the move beyond the CIFS
+Support for the CIFS protocol is clearly a characteristic element of Samba,
+ but in Samba4 this is extended: Samba4 moves beyond the CIFS
@@ -227,7 +228,7 @@
- protocol to also include the DCE-RPC
+ protocol to expose DCE-RPC
@@ -244,26 +245,25 @@
- that is carried over CIFS.
- This move to include new protocols and new transports (layered wrappings)
- for existing protocols is perhaps the most characteristic change.
+ over non-CIFS transports, such as directly on TCP/IP.
Perhaps reword the above.
Support for non-CIFS is a defining characteristic of Samba4.
-The first big change has been to answer DCE-RPC on non-CIFS transports.
- In previous versions of Windows networking, DCE-RPC had always been encountered
+In previous versions of Windows networking, DCE-RPC had always been encountered
as data flowing across named pipes, a concept existing in the file-system
and shared between hosts by the CIFS file-sharing protocol.
The change with Windows 2000 is that RPC became available directly on TCP/IP
-The challenge for this project was to add Kerberos to the protocols that
- Samba4 implements, and to create patches to other projects to allow them
- to cooperate with Samba4 in implementing this.
+In the same way that Samba must support the newer DCE-RPC over TCP, this
+ thesis shows how Kerberos is added to the protocols that Samba4 supports,
+ and to create patches to other projects to allow them to cooperate with
+ Samba4 in implementing this.
@@ -3296,11 +3296,11 @@
and assumptions in the original Heimdal code.
In particular, hdb-ldb is unique in Heimdal in that it may contain plain-text
passwords, not the hashed encryption keys.
- Storing the plaintext password is required when the `store password with
- reversable encryption' flag is set, and doing so by default has allowed
+ Storing the plain-text password is required when the `store password with
+ reversible encryption' flag is set, and doing so by default has allowed
easier initial development.
In this case, we `hash' the passwords on the fly, but we can also store
- the pre-hashed password if the plaintext is not available.
+ the pre-hashed password if the plain-text is not available.
These requirements required a minor code restructure, that has now been
included by Heimdal's developers into current snapshots.
More information about the samba-cvs