[Pkg-samba-maint] Bug#928355: Samba doesn't register the service connection when users access the shares

[Michael Tokarev]

Control: tag -1 + moreinfo

[ http://bugs.debian.org/928355 ]

On Thu, 2 May 2019 17:30:29 +0000 (UTC) Paulo Cesar <paulo_rallye at yahoo.com.br> wrote:
> Package: samba
> Version: 2:4.2.14+dfsg-0+deb8u12
> Severity: normal
> 
> Hello,
> 
> When searching for information about users who have connected to a certain share in our file sharing service, we realize that the Samba suite's "service.c" module no longer registers this connection in the service logs (/var/log/samba/log.smbd, in our configuration). In previous versions of Debian, as well as in the currently stable (stretch), the Samba daemon recorded the following message when a user connected to the share:
> [2019/04/30 09:36:16.865504,  2] ../source3/smbd/service.c:841(make_connection_snum)
>   Computer_Name (Source IP Address:Port) connect to service share_name initially as user username (uid=65534, gid=65534) (pid 6804)

> The messages previously displayed are no longer registered in the log file even with the policy "log level = 2 auth:3".

I know little about different samba protocols, but my quick check reveals this.

The message you mentioned above are generated by source3/smbd/smb2_service.c file.
This is SMB2 protocol, it looks like.  And it also looks to me like the current
protocol is SMB3, in source4/smb_server/smb/.

 From what I see on our servers, the same connection is used by multiple users, -
at least it is obvious that the same samba PID is used to handle connections
from multiple users.

I might be wrong, but it looks like there's no use nowadays for the *initial*
connection user.  Someone more knowlegeable about samba protocols might be able
to give more details, but to me it looks like we've lost the ability to associate
user with a connection due to *protocol* changes.

If that's the case, this bug report should be closed.

Thanks,

/mjt