4.2.4.4 GSS_WrapEx Examples

  • Article

The GSS_WrapEx() is specified in section 3.4.6. The following data is part of the security context state for the NTLM Session.

SeqNum for the message:

 0000000: 00 00 00 00                                       ••••

Plaintext data where conf_req_flag == TRUE and sign == TRUE:

 0000000: 50 00 6c 00 61 00 69 00 6e 00 74 00 65 00 78 00   P•l•a•i•n•t•e•x•
 0000010: 74 00                                             t•

The sealkey is created using SEALKEY() (section 3.4.5.3):

MD5(ConcatenationOf(RandomSessionKey, "session key to client-to-server sealing key magic constant")):

 0000000: 59 f6 00 97 3c c4 96 0a 25 48 0a 7c 19 6e 4c 58   Y.•.<─.•%H•.•nLX

The signkey is created using SIGNKEY() (section 3.4.5.2):

MD5(ConcatenationOf(RandomSessionKey, "session key to client-to-server signing key magic constant")):

 0000000: 47 88 dc 86 1b 47 82 f3 5d 43 fd 98 fe 1a 2d 39   G...•G..]C...•-9

The output message data and signature is created using SEAL() specified in section 3.4.3. Output_message will contain conf_state == TRUE, signed == TRUE and data:

Data:

 0000000: 54 e5 01 65 bf 19 36 dc 99 60 20 c1 81 1b 0f 06   T.•e.•6..`...•••
 0000010: fb 5f                                             √_

Checksum: HMAC_MD5(SigningKey, ConcatenationOf(SeqNum, Message))[0..7]:

 0000000: 70 35 28 51 f2 56 43 09                           p5(Q.VC•

Checksum: RC4(Checksum above):

 0000000: 7f b3 8e c5 c5 5d 49 76                     .....]Iv

Signature:

 0000000: 01 00 00 00 7f b3 8e c5 c5 5d 49 76 00 00 00 00   ••••.....]Iv••••