RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1690222 - smbclient man page needs update on RHEL7.6
Summary: smbclient man page needs update on RHEL7.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: samba
Version: 7.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: Andrej Dzilský
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 04:14 UTC by Keith Huynh
Modified: 2019-08-06 12:46 UTC (History)
4 users (show)

Fixed In Version: samba-4.9.1-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:45:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2099 0 None None None 2019-08-06 12:46:08 UTC
Samba Project 13857 0 None None None 2019-04-16 11:19:11 UTC

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
Note You need to log in before you can comment on or make changes to this bug.