formatting in the technical content. 5/16/2008 6.0.3 Editorial Changed language and formatting in the technical content. 6/20/2008 7.0 Updated and revised the technical content. 7/25/2008 8.0 Major Updated and revised the technical content. 8/29/2008 9.0 Major Updated and revised the technical content. 10/24/2008 9.0.1 Editorial Changed language and formatting in the technical content. 12/5/2008 10.0 Major Updated and revised the technical content. 1/16/2009 11.0 Major Updated and revised the technical content. 2/27/2009 12.0 Major Updated and revised the technical content. 4/10/2009 12.1 Clarified the meaning of the technical content.
5/22/2009 13.0 Major Updated and revised the technical content. 7/2/2009 13.1 Clarified the meaning of the technical content. 8/14/2009 13.2 Minor Clarified the meaning of the technical content. 9/25/2009 14.0 Major Updated and revised the technical content. 11/6/2009 15.0 Major Updated and revised the technical content. 12/18/2009 15.1 Minor Clarified the meaning of the technical content. 1/29/2010 15.2 Clarified the meaning of the technical content. 3/12/2010 16.0 Major Updated and revised the technical content. 4/23/2010 16.1 Minor Clarified the meaning of the technical content. 6/4/2010 16.2 Minor Clarified the meaning of the technical content. 7/16/2010 16.2 None No changes to the
meaning, language, or formatting of the technical content. 8/27/2010 16.2 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 16.2 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 17.0 Major Updated and revised the technical content. 1/7/2011 17.1 Minor Clarified the meaning of the technical content. 2/11/2011 17.2 Minor Clarified the meaning of the technical content. 3/25/2011 17.3 Minor Clarified the meaning of the technical content. 5/6/2011 17.3 None No changes to the meaning, language, or formatting of the technical content.
6/17/2011 17.4 Minor Clarified the meaning of the technical content. 9/23/2011 18.0 Major Updated and revised the technical content. 12/16/2011 19.0 Updated and revised the technical content. 3/30/2012 20.0 Major Updated and revised the technical content. 7/12/2012 21.0 Major Updated and revised the technical content. 10/25/2012 22.0 Major Updated and revised the technical content. 1/31/2013 23.0 Updated and revised the technical content. 8/8/2013 24.0 Major Updated and revised the technical content. 11/14/2013 25.0 Major Updated and revised the technical content. 2/13/2014 26.0 Major Updated and revised the technical content. 5/15/2014 26.0 None No changes to the
meaning, language, or formatting of the technical content. 6/30/2015 27.0 Major Significantly changed the technical content. 10/16/2015 27.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 28.0 Major Significantly changed the technical content. 6/1/2017 28.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 29.0 Major Significantly changed the technical content. 12/1/2017 29.0 None No changes to the meaning, language, or formatting of the technical content. 9/12/2018 30.0 Significantly changed the technical content.
MD5_HASH(M) Indicates the computation of an MD5 message digest of a binary blob ( section 4.1.1.2). NIL A zero-length string. 3.1.5.1.1, 3.1.5.1.2, 3.2.5.1.1, , 3.4.5.2 NONCE(N) Indicates the computation of an N-byte random number. Note The NTLM Authentication Protocol does not define the statistical properties of the random number generator. It is left to the discretion of the implementation to define the strength requirements of the NONCE(N) operation. 3.1.5.1.2, 3.2.5.1.1, 3.4.3 Computes a one-way function of the user's password to use as the response key. NTLM v1 and NTLM v2 define separate NTOWF functions in the NTLM v1 authentication and NTLM v2 authentication sections, respectively. 3.1.5.1.2, 3.3.1, 3.3.2 RC4(H, D) The RC4 Encryption Algorithm. To obtain this stream cipher that is licensed by RSA Data Security, Inc., contact this company. Indicates the encryption of data item D with the current or message key state, using the RC4 algorithm. H is the handle to a key state structure initialized by RC4INIT. 3.4.3, 3.4.4 RC4K(K,D) Indicates the encryption of data item D with the key K using the RC4 algorithm. Note The key for RC4 encryption in NTLM are defined in sections KXKEY, SIGNKEY, and SEALKEY, where they are created. 3.1.5.1.2, 3.4.4 RC4Init(H, K) Initialization of the RC4 key and handle to a key state structure for the session. 3.1.5.1.2, 3.2.5.1.2 SEALKEY(F, K, string1) Produces an encryption key from the as defined in sections KXKEY, SIGNKEY, and SEALKEY. 3.1.5.1.2, 3.4.5.3
81 81 10 Initialization 41 48 7 K KXKEY ( 63, 63) L 31 31 Local events 47 55 M Message processing 42 45 42 42 49 54 49 49 Messages 16 16 N 31 17 10 NTLM 12 13 13 69 34 16 36 37 36 NTLMv1 55 71 73 73 client challenge 74 76 75 55 NTLMv2 57 77 79 78 55 34 35 O Other local events 47 55 11 P 81 14 14 85 Protocol Details 39 R 10 10 10 14 30 S SEALKEY ( 63, 64) Security 81 81 58 Sequencing rules 42 45 42 42 49 54 49 49 Server 47 47 variables 48 47 48 48 55 49 54 49 49 55 49 54 49 49 55 48 Session security