| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
Move handling of datagram status with ntlm_crypto routines, this
way ntlm_seal_regen becomes an internal detail.
Also better separate exended security and legacy sign/seal crypto
state generation and general handling in sign/seal functions
|
|
|
|
| |
This structure keeps the crypto state closer to the crypto routines.
|
|
|
|
|
| |
Avoids the look of magic numbers everywhere, and give some useful
context to the code reader
|
|
|
|
|
|
| |
MS-NLMP 3.1.5.1.2 says a client must fail to communicate if NTLMv2
is used, Integrity or Confidentiality are required and NetBIOS Computer
or Domain Name are not present in the Challenge message from the server.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The target_info structure embedded in the NT Response message in NTLMv2
contains information needed to establish if the client has sent a valid
MIC. So we need to extract and return it if the caller requested it.
Also moves some wire structures definitions in common to be able to
reuse them.
|
|
|
|
|
| |
If integrity is requested by any party then the MIC, if requested by the
server will be generated, otherwise it will not be.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Thi re-encoded the target_info structure at the client side adding
additional provisions of MS-NLMP 3.1.5.2.1
That is:
- generate indication that a MIC is requested by the server
- add ClientSuppliedTargetName data
|
|
|
|
| |
This is useufl to use test vetors w/o altering them
|
|
|
|
| |
It is never and should never be touched so const char * is better.
|
|
|
|
|
| |
In connectionless mode (GSS_C_DATAGRAM_FLAG on) sealing keys
ust be rotated for each message.
|
| |
|
|
|
|
| |
For now works only for satndalone server with access to a password file.
|
| |
|
| |
|
| |
|
|
|
|
| |
Adds crypto function helpers needed by NTLM authentication
|
|
Implements functions to encode/decode NTLMSSP packets
|