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.
So is the standard samba distribution (NetBSD 7.0.1) insecure? Remedies? -- Steve Blinkhorn <[email protected]>
