Re: samba and Windows 10

[Brett Lymn <blymn%internode.on.net@localhost>]

On Thu, May 17, 2018 at 05:14:13PM +0000, Steve Blinkhorn wrote:
> The Windows 10 box I use alongside a clutch of NetBSD boxes is
> suddenly refusing to map my samba shares as disks, and refusing
> smbclient connections, saying they are SMBv1 which is insecure.   This
> happened without any warning, and has left me scratching around with
> ftp to do necessary transfers.   I normally have a couple of share
> permanently mounted, and my guess is, reading what information I can
> find, that somehow I have made no active use over the past couple of
> weeks, so Windows has silently disabled the relevant module.
> 

We use samba with windows 10 at $WORK (not on NetBSD unfortunately but
still samba)

As others have said, yes MS have quietly disabled smbv1.  It has long
been a hardening recommendation but now they have forced the issue.

Other things to watch are the settings for packet signing, it would
probably be best to this to sign if the server requires it (set to auto)
otherwise your connections may fail depending on the policy of the
windows machine.

> So is the standard samba distribution (NetBSD 7.0.1) insecure?
> Remedies?
> 

This is a combination of the whims of microsoft and the settings of your
samba.  Samba v4 definitely talks fine to windows 10 using smbv2.

-- 
Brett Lymn
Let go, or be dragged - Zen proverb.