diff options
| author | Christoph Zauner <christoph.zauner@sernet.de> | 2008-06-11 14:49:30 +0200 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2008-06-12 09:25:35 +0200 |
| commit | 8d3a451fd2c1ba831076f0f196c5324db57879a3 (patch) | |
| tree | 2e406282139a1a98abbae5fa9a283eff893aa02b /docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml | |
| parent | 8d15371de40f9b0ed6261d5c1541d71d42cf0182 (diff) | |
| download | samba-8d3a451fd2c1ba831076f0f196c5324db57879a3.tar.gz samba-8d3a451fd2c1ba831076f0f196c5324db57879a3.tar.bz2 samba-8d3a451fd2c1ba831076f0f196c5324db57879a3.zip | |
Samba3-HOWTO: Fix typos.
(This used to be commit 2391d999eb733bd8d12631478f4318608225cbb6)
Diffstat (limited to 'docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml')
| -rw-r--r-- | docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml index 8aea1775e3..0b90c925b8 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml @@ -245,7 +245,7 @@ authentication contexts in this way (WinDD is an example of an application that Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters in the account name are considered equivalent. They are said to be case-preserving, but not case significant. Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were -not necessarilty case-preserving. All Windows NT family systems treat passwords as case-preserving and +not necessarily case-preserving. All Windows NT family systems treat passwords as case-preserving and case-sensitive. </para> @@ -276,8 +276,8 @@ This is the default setting since Samba-2.2.x. In share-level security, the client authenticates itself separately for each share. It sends a password along with each tree connection request (share mount), but it does not explicitly send a username with this operation. The client expects a password to be associated with each share, independent of the user. This means -that Samba has to work out what username the client probably wants to use, the SMB server is not explicitly -sent the username. Some commercial SMB servers such as NT actually associate passwords directly with shares +that Samba has to work out what username the client probably wants to use, +because the username is not explicitly sent to the SMB server. Some commercial SMB servers such as NT actually associate passwords directly with shares in share-level security, but Samba always uses the UNIX authentication scheme where it is a username/password pair that is authenticated, not a share/password pair. </para> |