+++ This bug was initially created as a clone of Bug #617482 +++
Description of problem:
I'm using fusesmb with options large_read and big_writes. When I ties to copy file to network share of windows server, which requires packet signing (Microsoft network server: Digitally sign communications = Enabled), copying fails and only 32KB of file copied. Strarting fusesmb with debug option showed me error:
unique: 652, opcode: WRITE (16), nodeid: 79, insize: 32848
write 32768 bytes to 0 flags: 0x8001
smb_signing_good: BAD SIG: seq 1
SMB Signature verification failed on incoming packet!
write 16384 bytes to 0
unique: 652, success, outsize: 24
unique: 653, opcode: WRITE (16), nodeid: 79, insize: 16464
write 16384 bytes to 16384 flags: 0x8001
unique: 653, error: -22 (Invalid argument), outsize: 16
unique: 654, opcode: FLUSH (25), nodeid: 79, insize: 64
unique: 654, error: -38 (Function not implemented), outsize: 16
unique: 655, opcode: RELEASE (18), nodeid: 79, insize: 64
release flags: 0x8001
unique: 655, success, outsize: 16
If size of file is less than 32KB copy process vents OK.
When I switches packet signing off copy process vents OK.
When I mounts fusesmb without big_writes copy process vents OK too.
Same behaviour I observes if I copies files in KDE's dolphin file manager.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Turn on mandatory packet signing on windows server (Microsoft network server: Digitally sign communications (always) = Enabled in security policy/security options).
2. Mount windows shares using fusesmb -o large_read,big_writes or connect to share via dolphin.
3. Try to copy file (size > 32KB) to share.
Error occured and only 32KB of file copied.
File will copied OK.
Problem seems related to write segment size.