| commit | 8e4f16e975e192709f398c98650cbe9fe2a76261 | |
| author | Amin Azez <azez@ufomechanic.net> | |
| Mon, 10 Mar 2008 10:06:12 +0000 (10 10:06 +0000) | ||
| committer | Stefan Metzmacher <metze@samba.org> | |
| Fri, 18 Apr 2008 20:09:10 +0000 (18 22:09 +0200) | ||
| tree | 09cc4534dc72501cbedd5c0e397730cb20e1f758 | treesnapshot (tar.gz zip) |
| parent | d06eafea1a3e7fa61c94492cf504e6fd81da861d | commitdiff |
Flag smb messages array with AND_X and LARGE_REQUEST
If smb_messages flags show for which opcodes VWV(0)
signifies chaining modes, and also which opcodes can
have requests >64K then the bcc / req->in.data_size
fixup in smbsrv_recv_smb_request can be more safely
applied.
This fix permits nttrans requests >64K to be handled.
It is not yet clear if THAT is a good thing, but this
fix does the current thing more nicely.
If smb_messages flags show for which opcodes VWV(0)
signifies chaining modes, and also which opcodes can
have requests >64K then the bcc / req->in.data_size
fixup in smbsrv_recv_smb_request can be more safely
applied.
This fix permits nttrans requests >64K to be handled.
It is not yet clear if THAT is a good thing, but this
fix does the current thing more nicely.
| source/smb_server/smb/receive.c | diffblobblamehistory |