Updated patch for manpages, thanks to Jay
This commit is contained in:
parent
e282f99a96
commit
8875eee065
83
samba-3.0.23d-man.patch
Normal file
83
samba-3.0.23d-man.patch
Normal file
@ -0,0 +1,83 @@
|
||||
--- samba-3.0.23d/docs/manpages/ntlm_auth.1.man 2006-11-14 05:01:51.000000000 -0500
|
||||
+++ samba-3.0.23d/docs/manpages/ntlm_auth.1 2006-11-15 15:59:59.000000000 -0500
|
||||
@@ -105,17 +105,17 @@
|
||||
The username, expected to be in Samba's
|
||||
unix charset.
|
||||
.sp
|
||||
-\fBExample 1. \fRUsername: bob
|
||||
+\fBExample 1.\fR Username: bob
|
||||
.sp
|
||||
-\fBExample 2. \fRUsername:: Ym9i
|
||||
+\fBExample 2.\fR Username:: Ym9i
|
||||
.TP 3n
|
||||
Username
|
||||
The user's domain, expected to be in Samba's
|
||||
unix charset.
|
||||
.sp
|
||||
-\fBExample 3. \fRDomain: WORKGROUP
|
||||
+\fBExample 3.\fR Domain: WORKGROUP
|
||||
.sp
|
||||
-\fBExample 4. \fRDomain:: V09SS0dST1VQ
|
||||
+\fBExample 4.\fR Domain:: V09SS0dST1VQ
|
||||
.TP 3n
|
||||
Full-Username
|
||||
The fully qualified username, expected to be in Samba's
|
||||
@@ -123,16 +123,16 @@
|
||||
and qualified with the
|
||||
winbind separator.
|
||||
.sp
|
||||
-\fBExample 5. \fRFull-Username: WORKGROUP\bob
|
||||
+\fBExample 5.\fR Full-Username: WORKGROUP\bob
|
||||
.sp
|
||||
-\fBExample 6. \fRFull-Username:: V09SS0dST1VQYm9i
|
||||
+\fBExample 6.\fR Full-Username:: V09SS0dST1VQYm9i
|
||||
.TP 3n
|
||||
LANMAN-Challenge
|
||||
The 8 byte
|
||||
\fBLANMAN Challenge\fR
|
||||
value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client.
|
||||
.sp
|
||||
-\fBExample 7. \fRLANMAN-Challege: 0102030405060708
|
||||
+\fBExample 7.\fR LANMAN-Challege: 0102030405060708
|
||||
.TP 3n
|
||||
LANMAN-Response
|
||||
The 24 byte
|
||||
@@ -140,7 +140,7 @@
|
||||
value, calculated from the user's password and the supplied
|
||||
\fBLANMAN Challenge\fR. Typically, this is provided over the network by a client wishing to authenticate.
|
||||
.sp
|
||||
-\fBExample 8. \fRLANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
|
||||
+\fBExample 8.\fR LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
|
||||
.TP 3n
|
||||
NT-Response
|
||||
The >= 24 byte
|
||||
@@ -148,24 +148,24 @@
|
||||
calculated from the user's password and the supplied
|
||||
\fBLANMAN Challenge\fR. Typically, this is provided over the network by a client wishing to authenticate.
|
||||
.sp
|
||||
-\fBExample 9. \fRNT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
|
||||
+\fBExample 9.\fR NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
|
||||
.TP 3n
|
||||
Password
|
||||
The user's password. This would be provided by a network client, if the helper is being used in a legacy situation that exposes plaintext passwords in this way.
|
||||
.sp
|
||||
-\fBExample 10. \fRPassword: samba2
|
||||
+\fBExample 10.\fR Password: samba2
|
||||
.sp
|
||||
-\fBExample 11. \fRPassword:: c2FtYmEy
|
||||
+\fBExample 11.\fR Password:: c2FtYmEy
|
||||
.TP 3n
|
||||
Request-User-Session-Key
|
||||
Apon sucessful authenticaiton, return the user session key associated with the login.
|
||||
.sp
|
||||
-\fBExample 12. \fRRequest-User-Session-Key: Yes
|
||||
+\fBExample 12.\fR Request-User-Session-Key: Yes
|
||||
.TP 3n
|
||||
Request-LanMan-Session-Key
|
||||
Apon sucessful authenticaiton, return the LANMAN session key associated with the login.
|
||||
.sp
|
||||
-\fBExample 13. \fRRequest-LanMan-Session-Key: Yes
|
||||
+\fBExample 13.\fR Request-LanMan-Session-Key: Yes
|
||||
.sp
|
||||
.it 1 an-trap
|
||||
.nr an-no-space-flag 1
|
Loading…
Reference in New Issue
Block a user