Ubuntu 16.04 LTS: SMBStatus shows wrong information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba4 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
This bug affects Samba 4.3.11 as provided in Ubuntu 16.04 LTS.
Smbstatus does not display correct information for users connected to my server.
This information is known to Samba as it is indeed correctly logged in samba audit module, which I have enabled and the log does show the correct username, group and host.
Here is an example of wrong smbstatus output:
Samba version 4.3.11-Ubuntu
PID Username Group Machine Protocol Version
-------
21001 nobody nogroup 192.168.11.88 (ipv4:192.
And here is what it would normally look like:
31691 fsmith marketing 192.168.11.88 (ipv4:192.
If I read the issue correctly, this has already been patched and fixed upstream in in Samba 4.4.0 and higher
https:/
Please provide feedback and a possible fix as we use smbstatus all the time to track open files and who they are opened by and for a quick view at opened samba shares.
Thank you.
affects: | sddm (Ubuntu) → samba4 (Ubuntu) |
Hi Gonzalo,
first of all thank you that seems to be an issue and your help to make Ubuntu better is appreciated. We need to sort out if the change is acceptable as an SRU thou.
First of all the good news - it is not that all users would be broken: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- - 7.0.49: 48802) NT1 ------- ------- ------- ------- ------- ------- ------
$ sudo smbstatus
Samba version 4.3.11-Ubuntu
PID Username Group Machine Protocol Version
-------
31778 paelzer paelzer 10.7.0.49 (ipv4:10.
Service pid machine Connected at
-------
mediashare 31778 10.7.0.49 Fri Dec 8 10:07:03 2017
The linked bug suggests only SMB3_10 or SMB3_11 connections are affected.
I tried with various linux clients and forceing version 3 but never coudl reproduce.
Might i ask what client you use to trigger this issue?
Note: the upstream bug refers to the change affecting output which is meant to be parsed and therefore not meant to be changed in the stable releases. The same argument might affect us in backporting.
@Andreas - I subscribe you so you can consider this in the samba work