[Pkg-samba-maint] DO NOT REPLY [Bug 6230] 'force group' still broken in 3.3.2

samba-bugs at samba.org samba-bugs at samba.org
Thu Jun 4 00:47:18 UTC 2009


------- Comment #22 from korn-bugzilla.samba.org at elan.rulez.org  2009-06-03 19:47 CST -------
OK, please get http://elan.rulez.org/~korn/tmp/samba-vbox.tar.bz2 (bzip
compressed it to around 250M).

The size of the file is 262057706 bytes; md5: 4bcebd20a0d295beeb2cd8a6de4f0de8;
sha1: 927aaaaf724a135a307d30060344e9508dda6c36.

Please tell me when I can stop hosting it.

The tar contains the contents of a ~/.VirtualBox directory, including
virtualbox.xml, so be careful not to overwrite your own if you have one.

The virtual image is of a 64bit computer (to more closely match the environment
where I originally experienced the problem). All passwords (root, ldap admin
etc.) are "qazwsx". There is a test user called "guy" (whose password is also
qazwsx); he can log in, but with the current smb.conf can't access the
\\localhost\store share. If you comment out "force group" in smb.conf and
reload smbd, the "guy" user can access \\localhost\store again.

The error message is, as before, "denied due to security descriptor"; the samba
logs in /var/log/samba already contain at least one example, resulting from
experiments with "smbclient -U guy '\\localhost\store'".

I even renamed the share_info.tdb file once and retested, with the same result.

As far as I know, the virtualbox image contains no sensitive information. You
may have to adapt some configfiles (like /etc/apt/sources.list or /etc/hosts or
/etc/resolv.conf) to suit your own network environment though.

I'm sorry, but I couldn't think of a much simpler way to enable you to
experiment with a failing setup; if you can't run virtualbox for some reason, I
can arrange for this instance to be started and accessible to you from the

Please don't hesitate to tell me if there's anything more I can do to help.


Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.

More information about the Pkg-samba-maint mailing list