Changeset 862 for trunk/server/docs-xml/manpages-3/ntlm_auth.1.xml
- Timestamp:
- May 13, 2014, 11:39:04 AM (11 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
-
. (modified) (1 prop)
-
docs-xml/manpages-3/ntlm_auth.1.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 860
- Property svn:mergeinfo changed
-
trunk/server/docs-xml/manpages-3/ntlm_auth.1.xml
r752 r862 161 161 <variablelist> 162 162 <varlistentry> 163 <term>Username</term> 164 165 <listitem><para>The username, expected to be in 166 Samba's <smbconfoption name="unix charset"/>. 167 </para> 168 169 <para><example>Username: bob</example></para> 170 <para><example>Username:: Ym9i</example></para> 171 </listitem></varlistentry> 172 173 <varlistentry> 174 <term>NT-Domain</term> 175 <listitem><para>The user's domain, expected to be in 176 Samba's <smbconfoption name="unix charset"/>. 177 </para> 178 179 <para><example>NT-Domain: WORKGROUP</example></para> 180 <para><example>NT-Domain:: V09SS0dST1VQ</example></para> 181 </listitem></varlistentry> 182 183 <varlistentry> 184 <term>Full-Username</term> 185 <listitem><para>The fully qualified username, expected to be in 186 Samba's <smbconfoption name="unix charset"/> and qualified with the 187 <smbconfoption name="winbind separator"/>. 188 </para> 189 190 <para><example>Full-Username: WORKGROUP\bob</example></para> 191 <para><example>Full-Username:: V09SS0dST1VQYm9i</example></para> 192 </listitem></varlistentry> 193 194 <varlistentry> 195 <term>LANMAN-Challenge</term> 196 197 <listitem><para>The 8 byte <command>LANMAN Challenge</command> value, 198 generated randomly by the server, or (in cases such as 199 MSCHAPv2) generated in some way by both the server and 200 the client. 201 </para> 202 <para><example>LANMAN-Challenge: 0102030405060708</example></para> 203 </listitem></varlistentry> 204 205 <varlistentry> 206 <term>LANMAN-Response</term> 207 208 <listitem><para>The 24 byte <command>LANMAN Response</command> value, 209 calculated from the user's password and the supplied 210 <command>LANMAN Challenge</command>. Typically, this 211 is provided over the network by a client wishing to authenticate. 212 </para> 213 <para><example>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para> 214 215 </listitem></varlistentry> 216 217 <varlistentry> 218 <term>NT-Response</term> 219 <listitem><para>The >= 24 byte <command>NT Response</command> 220 calculated from the user's password and the supplied 221 <command>LANMAN Challenge</command>. Typically, this is 222 provided over the network by a client wishing to authenticate. 223 </para> 224 <para><example>NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para> 225 226 </listitem></varlistentry> 227 228 <varlistentry> 229 <term>Password</term> 230 <listitem><para>The user's password. This would be 231 provided by a network client, if the helper is being 232 used in a legacy situation that exposes plaintext 233 passwords in this way. 234 </para> 235 <para><example>Password: samba2</example></para> 236 <para><example>Password:: c2FtYmEy</example></para> 237 238 </listitem></varlistentry> 239 240 <varlistentry> 241 <term>Request-User-Session-Key</term> 242 <listitem><para>Upon successful authenticaiton, return 243 the user session key associated with the login. 244 </para> 245 <para><example>Request-User-Session-Key: Yes</example></para> 246 247 </listitem></varlistentry> 248 249 <varlistentry> 250 <term>Request-LanMan-Session-Key</term> 251 <listitem><para>Upon successful authenticaiton, return 252 the LANMAN session key associated with the login. 253 </para> 254 <para><example>Request-LanMan-Session-Key: Yes</example></para> 255 256 </listitem></varlistentry> 257 258 <para><warning>Implementers should take care to base64 encode 259 any data (such as usernames/passwords) that may contain malicous user data, such as 260 a newline. They may also need to decode strings from 261 the helper, which likewise may have been base64 encoded.</warning></para> 262 </variablelist> 263 163 <term>Username</term> 164 <listitem><para>The username, expected to be in 165 Samba's <smbconfoption name="unix charset"/>. 166 </para> 167 <varlistentry> 168 <term>Examples:</term> 169 <para>Username: bob</para> 170 <para>Username:: Ym9i</para> 171 </varlistentry> 172 </listitem> 173 </varlistentry> 174 175 <varlistentry> 176 <term>NT-Domain</term> 177 <listitem><para>The user's domain, expected to be in 178 Samba's <smbconfoption name="unix charset"/>. 179 </para> 180 181 <varlistentry> 182 <term>Examples:</term> 183 <para>NT-Domain: WORKGROUP</para> 184 <para>NT-Domain:: V09SS0dST1VQ</para> 185 </varlistentry> 186 </listitem> 187 </varlistentry> 188 189 <varlistentry> 190 <term>Full-Username</term> 191 <listitem><para>The fully qualified username, expected to be 192 in Samba's <smbconfoption name="unix charset"/> and qualified 193 with the <smbconfoption name="winbind separator"/>.</para> 194 <varlistentry> 195 <term>Examples:</term> 196 <para>Full-Username: WORKGROUP\bob</para> 197 <para>Full-Username:: V09SS0dST1VQYm9i</para> 198 </varlistentry> 199 </listitem> 200 </varlistentry> 201 202 <varlistentry> 203 <term>LANMAN-Challenge</term> 204 <listitem><para>The 8 byte <command>LANMAN Challenge</command> 205 value, generated randomly by the server, or (in cases such 206 as MSCHAPv2) generated in some way by both the server and 207 the client.</para> 208 <varlistentry> 209 <term>Examples:</term> 210 <para>LANMAN-Challenge: 0102030405060708</para> 211 </varlistentry> 212 </listitem> 213 </varlistentry> 214 215 <varlistentry> 216 <term>LANMAN-Response</term> 217 <listitem><para>The 24 byte <command>LANMAN Response</command> value, 218 calculated from the user's password and the supplied 219 <command>LANMAN Challenge</command>. Typically, this 220 is provided over the network by a client wishing to authenticate. 221 </para> 222 <varlistentry> 223 <term>Examples:</term> 224 <para>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</para> 225 </varlistentry> 226 </listitem> 227 </varlistentry> 228 229 <varlistentry> 230 <term>NT-Response</term> 231 <listitem><para>The >= 24 byte <command>NT Response</command> 232 calculated from the user's password and the supplied 233 <command>LANMAN Challenge</command>. Typically, this is 234 provided over the network by a client wishing to authenticate. 235 </para> 236 <varlistentry> 237 <term>Examples:</term> 238 <para>NT-Response: 0102030405060708090A0B0C0D0E0F10111213141516171</para> 239 </varlistentry> 240 </listitem> 241 </varlistentry> 242 243 <varlistentry> 244 <term>Password</term> 245 <listitem><para>The user's password. This would be 246 provided by a network client, if the helper is being 247 used in a legacy situation that exposes plaintext 248 passwords in this way.</para> 249 <varlistentry> 250 <term>Examples:</term> 251 <para>Password: samba2</para> 252 <para>Password:: c2FtYmEy</para> 253 </varlistentry> 254 </listitem> 255 </varlistentry> 256 257 <varlistentry> 258 <term>Request-User-Session-Key</term> 259 <listitem><para>Upon successful authenticaiton, return 260 the user session key associated with the login.</para> 261 <varlistentry> 262 <term>Examples:</term> 263 <para>Request-User-Session-Key: Yes</para> 264 </varlistentry> 265 </listitem> 266 </varlistentry> 267 268 <varlistentry> 269 <term>Request-LanMan-Session-Key</term> 270 <listitem><para>Upon successful authenticaiton, return 271 the LANMAN session key associated with the login. 272 </para> 273 <varlistentry> 274 <term>Examples:</term> 275 <para>Request-LanMan-Session-Key: Yes</para> 276 </varlistentry> 277 </listitem> 278 </varlistentry> 279 280 </variablelist> 264 281 </listitem> 265 282 </varlistentry> 266 </variablelist> 267 </listitem> 283 </variablelist> 284 <warning><para>Implementers should take care to base64 encode 285 any data (such as usernames/passwords) that may contain malicous user data, such as 286 a newline. They may also need to decode strings from 287 the helper, which likewise may have been base64 encoded.</para></warning> 288 </listitem> 268 289 </varlistentry> 269 290
Note:
See TracChangeset
for help on using the changeset viewer.
