diff options
| author | vorlon <vorlon@alioth.debian.org> | 2008-07-04 09:23:34 +0000 |
|---|---|---|
| committer | vorlon <vorlon@alioth.debian.org> | 2008-07-04 09:23:34 +0000 |
| commit | f9e6081383cfc8d4319afa4103dbe5abcaafa708 (patch) | |
| tree | 98b044e3cfabb6e4d9c1dc0ea59a57fb8ff42a85 /docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html | |
| parent | 6149bff465b36175e7fcc5900ca67c2631dd9bf1 (diff) | |
| download | samba-f9e6081383cfc8d4319afa4103dbe5abcaafa708.tar.gz | |
Load samba-3.2.0 into branches/samba/upstream-3.2.upstream/3.2.0-gobbleupstream/3.2.0
git-svn-id: svn://svn.debian.org/svn/pkg-samba/branches/samba/upstream-3.2@1981 fc4039ab-9d04-0410-8cac-899223bdd6b0
Diffstat (limited to 'docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html')
| -rw-r--r-- | docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html b/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html index 580421c25e..4552f36961 100644 --- a/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html +++ b/docs/htmldocs/Samba3-Developers-Guide/pwencrypt.html @@ -1,12 +1,12 @@ <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 13. LanMan and NT Password Encryption</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.1"><link rel="start" href="index.html" title="SAMBA Developers Guide"><link rel="up" href="pt03.html" title="Part III. Samba Subsystems"><link rel="prev" href="wins.html" title="Chapter 12. Samba WINS Internals"><link rel="next" href="pt04.html" title="Part IV. Debugging and tracing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 13. LanMan and NT Password Encryption</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="wins.html">Prev</a> </td><th width="60%" align="center">Part III. Samba Subsystems</th><td width="20%" align="right"> <a accesskey="n" href="pt04.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pwencrypt"></a>Chapter 13. LanMan and NT Password Encryption</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><br> <code class="email"><<a class="email" href="mailto:samba@samba.org">samba@samba.org</a>></code><br> - </p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pwencrypt.html#id2582367">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2582387">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2582472">The smbpasswd file</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2582367"></a>Introduction</h2></div></div></div><p>With the development of LanManager and Windows NT + </p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pwencrypt.html#id2553345">Introduction</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2553365">How does it work?</a></span></dt><dt><span class="sect1"><a href="pwencrypt.html#id2553450">The smbpasswd file</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553345"></a>Introduction</h2></div></div></div><p>With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able to validate user connections in exactly the same way as a LanManager or Windows NT server.</p><p>This document describes how the SMB password encryption algorithm works and what issues there are in choosing whether you want to use it. You should read it carefully, especially - the part about security and the "PROS and CONS" section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2582387"></a>How does it work?</h2></div></div></div><p>LanManager encryption is somewhat similar to UNIX + the part about security and the "PROS and CONS" section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553365"></a>How does it work?</h2></div></div></div><p>LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a hashed value of a user's password. This is created by taking the user's plaintext password, capitalising it, and either @@ -43,7 +43,7 @@ know the correct password and is denied access.</p><p>Note that the Samba server never knows or stores the cleartext of the user's password - just the 16 byte hashed values derived from it. Also note that the cleartext password or 16 byte hashed values - are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2582472"></a>The smbpasswd file</h2></div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol + are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553450"></a>The smbpasswd file</h2></div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. Unfortunately, as the UNIX password value is also a one way hash function (ie. it is impossible to retrieve the cleartext of the user's |