Samba 4.11.x has landed in the -unstable repo and will be synced to stable along with the GNOME-3.36 stack upgrade.

For most users, this will be a non-event, as everything should just work as usual.

However, since SMB1 is now officially deprecated by upstream, they can no longer guarantee that SMB1 will keep working, which means that any workarounds in place locally to downgrade to SMB1 might stop working with no notice in the future.

Consider yourselves warned.

Therefore, users still relying on SMB1 who might be affected by this are strongly urged to upgrade to at least the SMB2_02 protocol (introduced with Windows Vista / Server 2008) when connecting to other Samba instances if they can, as some older network appliances support this version in addition to SMB1.

In my latest commit I've downgraded the Solus Samba minimum allowed protocol from SMB2_10 to SMB2_02 to make things as simple as possible for users.

If you need to configure other non-Solus Samba clients on your network to use SMB2_02, the appropriate incantations in /etc/samba/smb.conf look like this:

client ipc min protocol = SMB2_02
client min protocol = SMB2_02

For shares on non-Solus Samba servers, the necessary incantation in /etc/samba/smb.conf looks like this:

server min protocol = SMB2_02

If you want to understand which protocol is negotiated with a Samba server and which version of Samba the server runs, you can add/edit the following stanza in the [global] section for the server in question:

server string = Samba server (version: %v, protocol: %R)

(All of the above configuration parameters are already present in the default Solus Samba configuration)

EDIT: Updated OP to reflect new defaults with samba-4.11.7-62 which was just published to -unstable.

Nooooooo. I currently use this workaround because otherwise the network shares from our legacy windows server at work don't work.
I guess this will no longer work then.

sudo echo "client min protocol = NT1" > /etc/samba/smb.conf
After every new installation.

Is there a new workaround? How can I connect to them?

  • ermo replied to this.

    logtom

    All this means is that any local SMB1 workarounds put in place per the Solus Samba HOWTO are no longer guaranteed to keep working by upstream. These workarounds are also being removed from the newest version of the Samba HOWTO because there's no point in documenting a scenario that isn't guaranteed to work.

    Note that this is not the same as upstream saying that SMB1 will definitely not keep working in the near future.

    You're just going to have to take your chances I guess.

    In any case, I'm going to change the default Solus Samba configuration to allow the SMB 2.02 protocol (Windows Vista / Server 2008) out of the box so as to help mitigate this issue.

    If your workplace relies on SMB1, you should really consider updating your infrastructure...

        ermo

        Thanks for your reply. I guess I will talk with our admin about this issue. Anyway thanks for posting this here so I won't be surprised after updating.

          2 months later