summaryrefslogtreecommitdiff
path: root/docs/htmldocs/ENCRYPTION.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/htmldocs/ENCRYPTION.html')
-rw-r--r--docs/htmldocs/ENCRYPTION.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/htmldocs/ENCRYPTION.html b/docs/htmldocs/ENCRYPTION.html
index f7424be11a..e4d3ef5fed 100644
--- a/docs/htmldocs/ENCRYPTION.html
+++ b/docs/htmldocs/ENCRYPTION.html
@@ -19,7 +19,7 @@ CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
-NAME="AEN1"
+NAME="PWENCRYPT"
>LanMan and NT Password Encryption in Samba 2.x</A
></H1
><HR></DIV
@@ -118,7 +118,7 @@ NAME="AEN18"
><P
>The unix and SMB password encryption techniques seem similar
on the surface. This similarity is, however, only skin deep. The unix
- scheme typically sends clear text passwords over the nextwork when
+ scheme typically sends clear text passwords over the network when
logging in. This is bad. The SMB encryption scheme never sends the
cleartext password over the network but it does store the 16 byte
hashed values on disk. This is also bad. Why? Because the 16 byte hashed
@@ -196,7 +196,7 @@ CLASS="EMPHASIS"
Microsoft SMB/CIFS clients support authentication via the
SMB Challenge/Response mechanism described here. Enabling
clear text authentication does not disable the ability
- of the client to particpate in encrypted authentication.</P
+ of the client to participate in encrypted authentication.</P
></TD
></TR
></TABLE