From 55abd936a838a4410899db76cb5530b0c4694dc9 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 10 Oct 2001 17:19:10 +0000 Subject: mega-merge from 2.2 (This used to be commit c76bf8ed3275e217d1b691879153fe9137bcbe38) --- docs/htmldocs/ENCRYPTION.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/htmldocs/ENCRYPTION.html') 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" >

LanMan and NT Password Encryption in Samba 2.x

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.