[Pkg-samba-maint] Bug#385372: This

[Steve Langasek]

Taking this out of the BTS; even if it is a bug, it's not related to the bug
report that this discussion is being held in.

On Tue, Jul 24, 2007 at 08:12:13PM +0800, Joe C. K. Yau wrote:
> On Tue Jul 24 17:41:45 2007,
> Steve Langasek <vorlon at debian.org> wrote:

> > With 'encrypt passwords = false' and 'valid users = %S', I am able to
> > connect to my home share using smbclient //localhost/vorlon.  I've tested
> > this with both the etch and sid versions of samba.

> > At this point, I'm inclined to assume that you have some other incorrect
> > configuration options enabled in your smb.conf, and that this is the source
> > of the problem you're having.  At least, there is no evidence of a bug here,
> > so I would recommend that you get in touch with the upstream support list
> > for further troubleshooting help.

> Thank you, Steve, for helping me out.  The preexec problem for logging
> has been solved.  A little typo causing it to fail.  Anyways, that part
> is alright now.

> As for the "valid users = %S" problem, the problem is still there.
> There shouldn't be any other setting in the configuration that causes
> problems as the smb.conf file that I attached in my previous message
> is all I have in the smb.conf.  Whenever the "valid users = %S" line
> is enabled, it stopped working.  Really clueless.

> <=========================v=v=v= Config (v3) =v=v=v=========================>

>  1>>   [global]
>  2>>     workgroup = AlwaysBIG
>  3>>     encrypt passwords = false
>  4>>     root preexec  = /bin/bash /etc/samba/conn_log.sh "%T: CONN s:%S p:%P %U@%m"
>  5>>     root postexec = /bin/bash /etc/samba/conn_log.sh "%T: DISC s:%S p:%P %U@%m"
>  6>> 
>  7>>   [homes]
>  8>>     comment = Home Directories
>  9>>     browseable = no
> 10>>     writable = yes
> 11>>     create mask = 0700
> 12>>     directory mask = 0700
> 13>>     valid users = %S

> <=========================^=^=^= Config (v3) =^=^=^=========================>

Ok, attached is the relevant diff when I pass my working test config, and
your non-working config, through testparm -s -v and compare them.  None of
them seem likely candidates to me, but I would suggest that you try adding
each one of these changed lines to your smb.conf one-by-one to see whether
they have an effect on your problem.

If not, I'm out of ideas, and you should really take it up with upstream.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/