s3:smbd: if we allow trans2 on the IPC$ share, then we have to allow transs2 too.

Otherwise we'll confuse the client signing engine, when we reply an error to each transs2.

metze
(cherry picked from commit e217138a36b1ba1eff164aecfa52ba6fe8864747)

diff --git a/source/smbd/process.c b/source/smbd/process.c
index 82d5cc916d05893fd23d5cef77e2255d9e57c53a..ad01a52b39cdc9fb4440a6ab757287f5290c1228 100644 (file)
--- a/source/smbd/process.c
+++ b/source/smbd/process.c
@@ -1033,7 +1033,7 @@ static const struct smb_message_struct {
 /* 0x30 */ { NULL, NULL, 0 },
 /* 0x31 */ { NULL, NULL, 0 },
 /* 0x32 */ { "SMBtrans2",reply_trans2, AS_USER | CAN_IPC },
-/* 0x33 */ { "SMBtranss2",reply_transs2, AS_USER},
+/* 0x33 */ { "SMBtranss2",reply_transs2, AS_USER | CAN_IPC},
 /* 0x34 */ { "SMBfindclose",reply_findclose,AS_USER},
 /* 0x35 */ { "SMBfindnclose",reply_findnclose,AS_USER},
 /* 0x36 */ { NULL, NULL, 0 },