gvfs can't list shares from smb servers that disabled SMB1

Bug #1828107 reported by Andreas Hasenack on 2019-05-07
This bug affects 12 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)

Bug Description

After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list.

Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it:

andreas@nsnx:~$ nmblookup -A
Looking up status of
 D-NO-SMB1 <00> - B <ACTIVE>
 D-NO-SMB1 <03> - B <ACTIVE>
 D-NO-SMB1 <20> - B <ACTIVE>
 ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>

 MAC Address = 00-00-00-00-00-00

andreas@nsnx:~$ smbclient -L -N
WARNING: The "syslog" option is deprecated

 Sharename Type Comment
 --------- ---- -------
 print$ Disk Printer Drivers
 pub_no_smb1 Disk
 IPC$ IPC IPC Service (d-no-smb1 server (Samba, Ubuntu))
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available

andreas@nsnx:~$ smbclient // -U ubuntu%ubuntu -m NT1
WARNING: The "syslog" option is deprecated
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

andreas@nsnx:~$ smbclient // -U ubuntu%ubuntu -m SMB2
WARNING: The "syslog" option is deprecated
Try "help" to get a list of possible commands.
smb: \> dir
  . D 0 Fri May 3 18:16:38 2019
  .. D 0 Fri May 3 18:15:24 2019
  hello.txt N 21 Fri May 3 18:16:12 2019
  hello-from-nsnx.txt A 9 Fri May 3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks available

summary: - gvfs can't browse smb servers that disabled SMB1
+ gvfs can't list shares from smb servers that disabled SMB1
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Changed in gvfs:
status: Unknown → New
Changed in gvfs (Ubuntu):
status: Confirmed → Triaged
BloodyIron (bloodyiron) wrote :

I too am experiencing this in Ubuntu 19.04.

BloodyIron (bloodyiron) wrote :

So... any word on this bug? :S Still getting it.

Andreas Hasenack (ahasenack) wrote :

Looks like I missed a notification in https://gitlab.gnome.org/GNOME/gvfs/issues/307, I'll followup there

BloodyIron (bloodyiron) wrote :

So I just upgraded to 19.10 and I am _STILL_ having this issue. I have had this issue now through two whole major releases! SMB1 being turned off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this really needs to get fixed!

I've been reporting this failure since April of 2019 :/ (started in another bug report)

BloodyIron (bloodyiron) wrote :

And as a reminder, my "solution" is to:

1. trigger the error by trying to browse to an SMB share with SMB1 disabled on the server-side
2. "pidof gvfsd-smb-browse"
3. "kill $PID" from above (regular kill, not -9)

It then works, I can actually get to shares.

I have to do this after _every_ reboot.

tags: added: desktop-lts-wishlist
BloodyIron (bloodyiron) wrote :

Can we please get this addressed already? This issue persists in 19.10 (haven't tested in 20.04 yet due to unrelated reasons)

Andreas Hasenack (ahasenack) wrote :

This will only get better once another discovery service is used, since SMB1 won't come back.

https://github.com/christgau/wsdd is something we could look into

BloodyIron (bloodyiron) wrote :

But once I nicely kill the process, I not only can connect to the share, I can still discover network shares. So, I don't really know how to explain that.

JORGETECH (jorgetech) wrote :

I believe the real issue is that libsmbclient is still using the SMB1/NT1 protocol as the maximum, the issue should be solved upstream since SMB1 is deprecated (disabled by default in newer Samba server versions).

BloodyIron (bloodyiron) wrote :

Really hope this gets solved soon, have to kill the process after browsing shares every time I reboot.

BloodyIron (bloodyiron) wrote :

STILL getting this error in Ubuntu 20.04. Just upgraded to 19.10 and I get this error immediately. How exactly is this not already upstreamed and fixed already??? >:|

Jonas Islander (wbbap-reg03) wrote :

Can confirm the bug is still present in Ubuntu 20.04.

Malte Deiseroth (deisi) wrote :

This Bug is embarrassing.

BloodyIron (bloodyiron) wrote :

Why has this STILL not been rolled out to 20.04??? It was fixed for 19.10, but still not for 20.04...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.