On Mon, Apr 24 2023, kasak <[email protected]> wrote:

[...]

> i'm sorry for the noise, but samba package in openbsd has some bug since
> 7.2

Don't be sorry, create a new thread for it instead of hijacking this
one. ;)

(Too late, so I have amended the subject of this mail.)

> It erroneously map "nobody" as a homes share when it should not.
>
> example config:
> /*
> [global]
>
> map to guest = Bad User
> [homes]
>
> browseable = no
>
> writable = yes
> */
>
> with this config, samba will return nobody as a home share:
>
> /*
>
> [kasak@kasakoff ~]$ smbclient -L \\\\172.16.12.111
> Password for [WORKGROUP\kasak]:
>
>     Sharename       Type      Comment
>     ---------       ----      -------
>     IPC$            IPC       IPC Service (Samba 4.17.6)
>     nobody          Disk      Home directory of nobody
> SMB1 disabled -- no workgroup available
>
> */
>
> it shouldn't be like that. And it was not, prior 7.2.
>
> I even tryed to create home directory for nobody user,

I suggest you don't do that.

> but it seems
> there is no way you can use it:
>
> [kasak@kasakoff ~]$ smbclient \\\\172.16.12.111\\nobody -U guest%guest
> tree connect failed: NT_STATUS_ACCESS_DENIED
>
> I have many other samba hosts, and I often use [homes] special share,
> but it never map "nobody" as a home share.
>
> So i think this is a bug somewhere, but i can't figure out from where it
> come from. All i know that it was ok in 7.1 and not ok since 7.2

No idea whether the behavior between 7.1 (samba-4.15.9) and 7.2
(samba-4.16.9) actually is different, maybe it was caused by an upstream
change or by some special interaction between samba and OpenBSD.  You
don't state why this share being listed is a problem.

I don't use samba anymore, I just handle updates of the port.
Maybe other folks will chime in.  Since the problem you mention didn't
appear with this update to 4.17.7, I have committed the update.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply via email to