Bug 1690222

Summary: smbclient man page needs update on RHEL7.6
Product: Red Hat Enterprise Linux 7 Reporter: Keith Huynh <khuynh>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED ERRATA QA Contact: Andrej Dzilský <adzilsky>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.6CC: asn, gdeschner, jarrpa, jstephen
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: samba-4.9.1-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:45:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Keith Huynh 2019-03-19 04:14:28 UTC
Description of problem:

With samba-client-4.8.3-4.el7.x86_64, the default version of the Server Message Block (SMB) protocol has been changed from SMB1 to be auto-negotiated to the highest supported versions SMB2 or SMB3 but according to man page of smbclient, it states that by default, this is set to SMB1. With latest 'samba-client-4.8.3-4.el7.x86_64' package, man page of smbclient should stated that by default SMB will be auto-negotiated to the highest supported versions SMB2 or SMB3 instead of stating that by default this is set to NT1.



# man smbclient

-m|--max-protocol protocol:
This allows the user to select the highest SMB protocol level that smbclient will use to connect to the server. By default this is set to NT1, which is the highest available SMB1 protocol. To connect using SMB2 or SMB3 protocol, use the strings SMB2 or SMB3 respectively. Note that to connect to a Windows 2012 server with encrypted transport selecting a max-protocol of SMB3 is required.

Executing smbclient command below without specifying -m SMB2/SMB3 it will use SMBv3 as default.

# smbclient  '\\CIFS_share\' -U XXXX

Autonegotiate cifs protocol to the highest protocol allowed by smb-server. 
https://access.redhat.com/solutions/3610601

Version-Release number of selected component (if applicable):
samba-client-4.8.3-4.el7.x86_64
kernel-3.10.0-957.el7 or later

How reproducible:

Very simple to reproduce. Installed these packages, kernel-3.10.0-957.el7 and samba-client-4.8.3-4.el7.x86_64 and check man page of smbclient and search for -m option in man page.

Steps to Reproduce:
1. Installed samba-client-4.8.3-4.el7.x86_64 and kernel-3.10.0-957.el7 on RHEL7.6 VM 
2. Do man page on smbclient and look for -m option.

-m|--max-protocol protocol:
This allows the user to select the highest SMB protocol level that smbclient will use to connect to the server. By default this is set to NT1, which is the highest available SMB1 protocol. To connect using SMB2 or SMB3 protocol, use the strings SMB2 or SMB3 respectively. Note that to connect to a Windows 2012 server with encrypted transport selecting a max-protocol of SMB3 is required.

3.

Actual results:

Need to review man page of smblclient especially -m option information regarding default SMB protocol used by smblclient command. With RHEL7.6, man page should stated that default SMB protocol used is to auto-negotiate to highest SMB protocol either SMB2 or SMB3 instead of by default this is set to NT1.

Expected results:

With RHEL7.6, man page of smbclient should stated that default SMB protocol used is to auto-negotiate to highest SMB protocol either SMB2 or SMB3 instead of by default this is set to NT1.

Additional info:

Comment 5 Andrej Dzilský 2019-04-16 11:36:16 UTC
Verified.

Comment 7 errata-xmlrpc 2019-08-06 12:45:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2099