Metze,
In order to track document bugs properly, I will be following up on these new
questions in two separate cases. I will start a new thread for each case:
112082370902333 SMB3 encryption of SESSION_SETUP (for reauth/or channel
binding) and TREE_CONNECT
112082371227089 SMB3 encryption and Opl
Hi Edgar,
thanks for the answers, I have some more questions inline.
> What about async responses with STATUS_PENDING, are they also encrypted?
>
> [Answer]
> Yes. The exceptions that are not encrypted are SMB2 NEGOTIATE, SMB2
> SESSION_SETUP or SMB2 TREE_CONNECT as documented in 3.2.4.1.8 E
Metze,
Please find our answers as follows. A future release of MS-SMB2 will further
clarify SMB3 encryption, especially with specifics for compounded messages.
Since one session key is used for the encrypted message, it is expected that
all operations in this message belong to the SessionId in
Metze,
Slight change in plan to load balance on this side: my colleague Edgar (copied)
will help you on this issue.
Bryan
-Original Message-
From: Bryan Burgin
Sent: Wednesday, August 08, 2012 1:17 PM
To: 'Stefan (metze) Metzmacher'
Cc: p...@tridgell.net; cifs-protocol@cifs.org; MSSolv
[dochelp to bcc]
[adding case number and casemail]
Hi Metze,
We created the case 112080864018345 to track this issue, which I will help you
with.
Thanks.
Bryan
-Original Message-
From: Stefan (metze) Metzmacher [mailto:me...@samba.org]
Sent: Wednesday, August 08, 2012 9:38 AM
To: Int
