added a sent_oplock_break element to Files[] as a paranoia check so we

can't sent a oplock break twice on the same file.

changed some debug levels in the oplock code to level 0 so we can
track down a bug

zero the returned Files[] entry in find_free_file()

don't try to overcome client bugs in the handling of non-encrypted
passwords if in server level security mode

added paranoid null termination of password buffers

slight change to my ajt_panic() routine
(This used to be commit e360c79c9cec681c4609783019749773d3e79386)

1 files changed, 1 insertions, 0 deletions

diff --git a/source3/include/smb.h b/source3/include/smb.h
index 49854a2512..bd60c1077a 100644
--- a/source3/include/smb.h
+++ b/source3/include/smb.h
@@ -1454,6 +1454,7 @@ typedef struct
   BOOL print_file;
   BOOL modified;
   BOOL granted_oplock;
+  BOOL sent_oplock_break;
   char *name;
 } files_struct;