Re: [cifs-protocol] [REG:111062056241038] SMB1 maximum packet size with signing enabled

2011-06-21 Thread Jeff Layton
On Mon, 20 Jun 2011 22:11:57 + Hongwei Sun hongw...@microsoft.com wrote: Moving Interoperability Documentation Help (dochelp) to bcc. Hi, all This is an expected behavior. I have a blog about this topic that should explain the behaviors you have observed

Re: [cifs-protocol] [REG:111061756137964] Encryption of the key for netsh branchcache” importkey and exportkey.

2011-06-21 Thread Edgar Olougouna
Chris, Please let me know whether this helps. QUESTION 1: From what input is the Initialization Vector (IV) derived? Is it constant, derived from the initial passphrase, or derived from the SHA256 of the passphrase? QUESTION 2: What algorithm is used to derive the IV

[cifs-protocol] [REG:111061070310825] RE: [MS-PCCRC]: Handling of multi-range Range: headers is undefined.

2011-06-21 Thread Obaid Farooqi
Hi Chris: We have finished our investigation on your question regarding the response to a multi-range request. I discussed the issue with product group and here is what they think is the proper answer. The BranchCache content information format does not support multi-range requests

Re: [cifs-protocol] [REG:111061070310825] RE: [MS-PCCRC]: Handling of multi-range Range: headers is undefined.

2011-06-21 Thread Christopher R. Hertel
Obaid, I have a concern about the wording of the sample text your team provided. It is not necessary for the Branchcache content information format to support multi-range requests. The response to a multi-range request could clearly be sent as separate content information messages in a