[PATCH] Add -e encryption support to SMB3 client protocol support, plus documentation updates.

[Michael Adam]

I am currently reviewing the patchset.
And it looks good.

I am only wondering about the (sneaked in) change for thei
iosize command:

Originally 0x400 -- 0xFFFF00 was allowed.
Now suddenly 0 -- 0xFFFF00 is allowed.
with 0 meaning server controlled.
Can it be that any x with 0 < x < 0x400
is mapped to 0x400 (the original minimum)
implicitly?

And in the manpage, only the SMB1 limit
is described, not the (lack of) limit in
the SMB2+ case.

I'll do more testing and will follow up later..

Cheers - Michael

On 2013-08-16 at 17:06 -0700, Jeremy Allison wrote:
> This patchset adds support for --encrypt, or -e command
> line options to smbclient and smbcacls when SMB3 protocol
> is requested using -mSMB3.
> 
> It also adds a new "timeout" command and -t option to smbclient
> to set the per-operation timeout.
> 
> This is needed as once SMB3 encryption is selected the server
> response time can be very slow when requesting large numbers
> (256) of large encrypted packets (1MB) from a Windows 2012
> virtual machine. This allows a user to tune their allowable
> wait time.
> 
> Also contains documentation updates for the changes made
> to complete SMB2+ support in our client tools.
> 
> Please review and push if you're happy.
> 
> Cheers,
> 
> 	Jeremy.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 215 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20130820/515cbbd4/attachment.pgp>