[cifs-protocol] [REG:112080864018345] SMB3 encryption over multiple requests
edgaro at microsoft.com
Thu Aug 23 14:05:45 MDT 2012
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 Oplock/Lease break notifications
From: Stefan (metze) Metzmacher [mailto:metze at samba.org]
Sent: Wednesday, August 22, 2012 9:19 AM
To: Edgar Olougouna
Cc: pfif at tridgell.net; cifs-protocol at cifs.org
Subject: Re: [REG:112080864018345] SMB3 encryption over multiple requests
thanks for the answers, I have some more questions inline.
> What about async responses with STATUS_PENDING, are they also encrypted?
> Yes. The exceptions that are not encrypted are SMB2 NEGOTIATE, SMB2 SESSION_SETUP or SMB2 TREE_CONNECT as documented in 22.214.171.124.8 Encrypting the Message, 126.96.36.199.4 Encrypting the Message.
Windows doesn't complain if the client encrypt SESSION_SETUP (for reauth/or channel bind) and TREE_CONNECTS.
> How does it work, when the last request in a compound chain goes async?
> There is no change of processing rules for the encryption due to the last request in a compounded chain going async.
> Are Oplock/Lease Break Notifications encrypted?
> [Answer] Yes, see previous answer and references.
For Oplocks the server known the session from the file_id, but what session is used for leases?
To my understanding a lease key can be shared between sessions, is that correct?
More information about the cifs-protocol