[Bug 1416906] Re: force user no longer works
Chris J Arges
1416906 at bugs.launchpad.net
Thu Feb 12 21:59:19 UTC 2015
Hello Gerald, or anyone else affected,
Accepted samba into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-
1ubuntu2.14.04.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: samba (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1416906
Title:
force user no longer works
Status in samba package in Ubuntu:
Fix Released
Status in samba source package in Trusty:
Fix Committed
Bug description:
[Impact]
* Users are no longer able to use the force user or force group options in the smb.conf. This can prevent users from accessing shares without first having to login with a valid login.
[Test Case]
1. Create a directory /tmp/ubuntu
2. chown ubuntu:ubuntu /tmp/ubuntu
3. Add a section to the smb.conf like so.
[Ubuntutest]
comment = Ubuntutest
path = /tmp/ubuntu
browseable = yes
read only = no
guest ok = yes
force user = ubuntu
4. Make sure the ubuntu user has access to the directory from the server.
5. Attempt to access the share
6. Create a file
7. Verify the file is owned by ubuntu.
*Note: this does not seem to be testable from the samba-client command
line tool as it succeeds both before and after the patch.
[Regression Potential]
* Minimal. The fix is to use vuser->session_info instead of conn->session_info, when checking permissions. This seems like it should be fairly isolated to the initial permissions checks.
[Other Info]
* Pretty straightforward cherry-pick of upstream solution.
______________________________________________________
There is nasty regression bug in samba 4.1.6
That prevents the use of the "force user" option.
https://bugzilla.samba.org/show_bug.cgi?id=9878
It has been fixed in 4.1.7.
For now I installed samba from: ppa:linux-schools/backports
In order to get things working again.
Gérald
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1416906/+subscriptions
More information about the foundations-bugs
mailing list