| commit | 1ab23ac1e7c1f9a6f5c341c3b97b6035a17a762c | |
| author | Stefan Metzmacher <metze@samba.org> | |
| Mon, 13 Oct 2014 08:39:45 +0000 (13 10:39 +0200) | ||
| committer | Jeremy Allison <jra@samba.org> | |
| Thu, 16 Oct 2014 17:30:04 +0000 (16 19:30 +0200) | ||
| tree | f6252002fa4d1c7b4c539a4461b8d4966c5a21da | treesnapshot (tar.gz zip) |
| parent | d81d77ae03d1631b408c43d8d34953c663e8ac3b | commitdiff |
libcli/smb: use conn->smb2.server.cipher != 0 instead of conn->smb2.server.capabilities & SMB2_CAP_ENCRYPTION
SMB 3.10 servers don't report SMB2_CAP_ENCRYPTION anymore.
So using conn->smb2.server.cipher != 0 is a more consistent way to decide if
encryption is supported on the connection.
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
SMB 3.10 servers don't report SMB2_CAP_ENCRYPTION anymore.
So using conn->smb2.server.cipher != 0 is a more consistent way to decide if
encryption is supported on the connection.
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
| libcli/smb/smbXcli_base.c | diffblobblamehistory |