mirror of
https://github.com/samba-team/samba.git
synced 2024-12-23 17:34:34 +03:00
44cc9fb0e0
We fail this on SMB2 for a subtle reason. Our client code called from smbclient only sets the SMB2_HDR_FLAG_DFS flag in the outgoing packet on the SMB2_CREATE call, and SMB2 rename does the following operations: SMB2_CREATE(src_path) // We set SMB2_HDR_FLAG_DFS here for a MSDFS share. SMB2_SETINFO: SMB2_FILE_RENAME_INFO(dst_path). // We don't set SMB2_HDR_FLAG_DFS However, from smbclient, dst_path is a MSDFS path but we don't set the flag, so even though the rename code inside smbd will cope with a MSDFS path (as used in the SMB1 SMBmv call) it fails as the correct flag isn't set. Add knownfail selftest/knownfail.d/msdfs-rename. Note we need to add the new test to "selftest/knownfail.d/smb1-tests" as test_smbclient_s3.sh is run against the (ad_member|nt4_member) environments first using NT1 (SMB1) protocol and then using SMB3, but the (ad_member|nt4_member) environments don't support SMB1. Seems a bit strange to me, but all the other SMB1 tests inside test_smbclient_s3.sh have already been added to "selftest/knownfail.d/smb1-tests" so just go with the test environment. BUG: https://bugzilla.samba.org/show_bug.cgi?id=14169 Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Noel Power <npower@samba.org> |
||
---|---|---|
.. | ||
tests | ||
count_80_col.pl | ||
creategroup | ||
fix_bool.pl | ||
format_indent.sh | ||
makeunicodecasemap.awk | ||
mknissmbpasswd.sh | ||
mknissmbpwdtbl.sh | ||
mksmbpasswd.sh | ||
mksyms.awk | ||
mksyms.sh | ||
scancvslog.pl | ||
smbaddshare | ||
smbchangeshare | ||
smbdeleteshare | ||
smbtar | ||
strip_trail_ws.pl | ||
updatesmbpasswd.sh | ||
wscript_build |