22 Sep
2018
22 Sep
'18
2:32 p.m.
On 22 September 2018 18:23:00 BST, Gary Gwin <garygwin@gmail.com> wrote:
During the chatty inner-tunnel MSCHAPv2 negotiation, the get NT hash API is invoked twice in requests 7 and 8, which works, but with unnecessary script and API load. I can eliminate the second invocation in step 8 by checking the request EAP-Message for length. That feels fragile. There must be a better way to detect state to determine we're in request 8.
Put the hash in the session-state list, but only if it's not already there? -- Matthew