Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1452003 - smbclient kills the connection when receives ioctl()-reponse STATUS_NOT_SUPPORTED
smbclient kills the connection when receives ioctl()-reponse STATUS_NOT_SUPPO...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: samba (Show other bugs)
7.4
x86_64 Linux
urgent Severity urgent
: rc
: ---
Assigned To: Andreas Schneider
Andrej Dzilský
: ZStream
: 1452028 (view as bug list)
Depends On:
Blocks: 1484723
  Show dependency treegraph
 
Reported: 2017-05-18 03:02 EDT by amitkuma
Modified: 2018-04-10 13:29 EDT (History)
7 users (show)

See Also:
Fixed In Version: samba-4.6.2-10.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1484723 (view as bug list)
Environment:
Last Closed: 2018-04-10 13:28:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Samba Project 12808 None None None 2017-05-31 04:31 EDT
Red Hat Product Errata RHBA-2018:0937 None None None 2018-04-10 13:29 EDT

  None (edit)
Description amitkuma 2017-05-18 03:02:51 EDT
Description of problem:
    [netApps SMB-server]                       [smb-Client]
                |      =SMB 2=                    |
                |                                 |  
                | <=FSCTL_VALIDATE_NEGOTIATE_INFO=|
                | =STATUS_NOT_SUPPORTED=>         | Drops Connection
                | <=TCP Fin=                      |

Either there should be option to disable the option to revalidate server capabilities by sending FSCTL_VALIDATE_NEGOTIATE_INFO.
OR smbclient should not drop the connection after getting STATUS_NOT_SUPPORTED from samba-server.

Version-Release number of selected component (if applicable):
smbclient-4.4.4-12.el7_3

How reproducible:
Always

Steps to Reproduce:
1. Configure samba server not having SMB3 enabled, speciafically returing STATUS_NOT_SUPPORTED for FSCTL_VALIDATE_NEGOTIATE_INFO request.
2. Connect using smbclient. client will send FSCTL_VALIDATE_NEGOTIATE_INFO.
3. On reception of STATUS_NOT_SUPPORTED, client will drop the connection

Actual results:
Connection drop

Expected results:
Connection should not be dropped

Additional info:
Comment 2 Andreas Schneider 2017-05-30 11:03:59 EDT
We have a patch for this. We could create a test package for this. Can the customer test the patch and report feedback?
Comment 3 amitkuma 2017-05-31 01:32:56 EDT
Hello Andreas,

Customer is willing to test the patch in his Test Env.

I would be looking forward for 1 patch having code changes for:
1. Current bugzilla. (as you mentioned you have patch)
2. And this https://bugzilla.redhat.com/show_bug.cgi?id=1452028 Also.

Thanks
Amit
Comment 13 Andreas Schneider 2017-08-17 10:18:29 EDT
This bug is not part of RHEL 7.4. As you can see it is considered for RHEL 7.5. We did not get positive feedback that the fix works in time ...
Comment 14 amitkuma 2017-08-21 09:43:42 EDT
Hello Andreas,

Since Issue appeared in 7.3 and we provided test packs having "samba-libs-4.6.2-4.1.el7.x86_64", which was released on 7.4

Hence customer was expecting fix on 7.4, since samba-4.6 is part of 7.4.
Even in comment#6 you mentioned to run test-rpms on 7.4.

But now fix is not in 7.4, what rest can be done?

Thanks
Comment 21 Andreas Schneider 2017-09-05 10:19:36 EDT
*** Bug 1452028 has been marked as a duplicate of this bug. ***
Comment 25 errata-xmlrpc 2018-04-10 13:28:22 EDT
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/RHBA-2018:0937

Note You need to log in before you can comment on or make changes to this bug.