From 3fe884c26c772fca65470c45540d37a58deda403 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Wed, 28 Apr 2004 13:17:28 +0000 Subject: r390: added my best guess for how session keys are supposed to work when you use NTLMSSP sign or seal at the RPC layer It doesn't work yet, but then again neither does the old code (which just assumed the SMB session key was used, which of course makes no sense on a ncacn_ip_tcp connection) (This used to be commit e8782329269bc78d36d8ca83fb7a4e38b9c6b167) --- source4/librpc/rpc/dcerpc_schannel.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'source4/librpc/rpc/dcerpc_schannel.c') diff --git a/source4/librpc/rpc/dcerpc_schannel.c b/source4/librpc/rpc/dcerpc_schannel.c index 2a4c0a6bb1..504c8dfd6f 100644 --- a/source4/librpc/rpc/dcerpc_schannel.c +++ b/source4/librpc/rpc/dcerpc_schannel.c @@ -56,6 +56,12 @@ static NTSTATUS schan_sign_packet(struct dcerpc_security *dcerpc_security, return schannel_sign_packet(schannel_state, data, length, sig); } +static NTSTATUS schan_session_key(struct dcerpc_security *dcerpc_security, + uint8 session_key[16]) +{ + return NT_STATUS_NOT_IMPLEMENTED; +} + static void schan_security_end(struct dcerpc_security *dcerpc_security) { struct schannel_state *schannel_state = dcerpc_security->private; @@ -232,6 +238,7 @@ NTSTATUS dcerpc_bind_auth_schannel_key(struct dcerpc_pipe *p, p->security_state->check_packet = schan_check_packet; p->security_state->seal_packet = schan_seal_packet; p->security_state->sign_packet = schan_sign_packet; + p->security_state->session_key = schan_session_key; p->security_state->security_end = schan_security_end; done: -- cgit