Andrew Tridgell 3854b5e614 changed BCC handling for SMBwriteX to handle broken MacOSX client ...

see bug #6610

The MacOSX SMB client sets the BCC value in SMBwriteX calls to zero
instead of the correct size. Checking against WindowsXP, I've found
that Windows uses the maximum of the computed buffer size and the
given BCC value. I've changed Samba4 to do the same to allow MacOSX to
work.

I've limited this change to non-chained packets to ensure we don't get
the possibility of exploits based on overlapping chained requests

2009-08-05 20:24:01 +10:00

..

smb

changed BCC handling for SMBwriteX to handle broken MacOSX client

2009-08-05 20:24:01 +10:00

smb2

s4:smb2srv: don't allow the related flag on the first request in a compounded chain

2009-06-09 19:33:46 +02:00

blob.c

Remove unused include param/param.h.

2008-10-24 16:37:56 +02:00

config.mk

Fix two remaining missing symbols in smbtorture4.

2008-12-22 23:00:10 +01:00

handle.c

Fix include paths to new location of libutil.

2008-10-11 21:31:42 +02:00

management.c

s4:irpc: avoid c++ reserved word 'private'

2009-02-01 00:17:20 +01:00

session.c

Fix include paths to new location of libutil.

2008-10-11 21:31:42 +02:00

smb_samba3.c

Fix the mess with ldb includes.

2009-01-30 01:02:03 -05:00

smb_server.c

s4:smb_server: initialy read the first 4 bytes only

2009-05-20 10:16:43 +02:00

smb_server.h

s4:lib/tevent: rename structs

2008-12-29 20:46:40 +01:00

tcon.c

Fix include paths to new location of libutil.

2008-10-11 21:31:42 +02:00