Re: upgrading to latest samba

[Mike Pumford <mpumford%mudcovered.org.uk@localhost>]

On 18/06/2018 16:46, Steve Blinkhorn wrote:
> I upgraded to Version 4.6.8 of the samba suite from the Q1 binary
> collection for amd64 (7.0), and have finally got back to the condition
> I was in vis a vis my Windows 10 box before it got stroppy and refused
> to connect either way.   I found the following:
>
> The libraries were installed into /usr/pkg/lib/samba/private, where
> they were inaccessible to the binaries.   I made hard links for them
> in /usr/pkg/lib.
> I think the perms generated by the package are wrong. If you do:

chmod 711 /usr/pkg/lib/samba/private

Then the binaries will work without any symlinks and also without 
exposing the folder contents to prying eyes. Not sure why this folder is 
so locked down on NetBSD. The FreeBSD and linux samba packages don't do 
this and FreeBSD actually makes the folder world and group readable as 
well.

> The smb password file was either trashed or became inaccessible.
> Whichever, I had to "smbpasswd -a unsername" for each account.
>
> I have yet to get a satisfactory result from setting the protocol in
> smb.conf, so to star the daemon I do "smbd -D --option=protocol=SMB3".
>
> For smbclient I use "smbclient -m SMB3 -U myuser //mywindowsbox/Users"
Adding:
client max protocol = SMB3

to the [global] section of /usr/pkg/etc/samba/smb.conf seems to work for 
me here. Without it I get:
protocol negotiation failed: NT_STATUS_CONNECTION_RESET

With it I get challenged for a password and when I give the correct one 
smbclient can then access the filesystem.


The other massive flaw in the NetBSD samba package is its utter failure 
to install any of the man pages. :(

Mike