As the encryption is stream based there's no reason

oplock breaks can't be encrypted. If we have multiple
contexts I should probably attach them to the connection
struct, but for now use the global context number.
Jeremy.
(This used to be commit 5b4b335ed0d1dc738f1f099e5c638361f3aede07)

1 files changed, 9 insertions, 0 deletions

diff --git a/source3/smbd/seal.c b/source3/smbd/seal.c
index 14a427bb9c..24ecb77fd5 100644
--- a/source3/smbd/seal.c
+++ b/source3/smbd/seal.c
@@ -48,6 +48,15 @@ bool srv_encryption_on(void)
 }
 
 /******************************************************************************
+ Return global enc context - this must change if we ever do multiple contexts.
+******************************************************************************/
+
+uint16 srv_enc_ctx(void)
+{
+	return srv_trans_enc_ctx->es->enc_ctx_num;
+}
+
+/******************************************************************************
  Create an auth_ntlmssp_state and ensure pointer copy is correct.
 ******************************************************************************/