diff options
| author | Volker Lendecke <vl@samba.org> | 2010-02-28 18:45:41 +0100 |
|---|---|---|
| committer | Volker Lendecke <vl@samba.org> | 2010-02-28 18:49:59 +0100 |
| commit | 9ad1b4cda04269dd50a719b4f65de2579d0da220 (patch) | |
| tree | 64d186d158f610379e1d63fc8cde59ee3d2b5dba /selftest/target/Windows.pm | |
| parent | fb98f60594b6cabc52d0f2f49eda08f793ba4748 (diff) | |
| download | samba-9ad1b4cda04269dd50a719b4f65de2579d0da220.tar.gz samba-9ad1b4cda04269dd50a719b4f65de2579d0da220.tar.bz2 samba-9ad1b4cda04269dd50a719b4f65de2579d0da220.zip | |
s3: Fix the CHAIN1 torture test
I've tried to solve this just within cli_smb_recv(), but I could not find a way
to sanely determine when we are receiving the last entry in the chain just from
looking at the blob. This solves it in an a bit more brutal way...
Diffstat (limited to 'selftest/target/Windows.pm')
0 files changed, 0 insertions, 0 deletions