Samba 4.1.6 not working after upgrade from 3.6.x - Fedora 20

[Jeremy Allison]

On Mon, Mar 17, 2014 at 02:08:08PM -0700, Jeremy Allison wrote:
> On Mon, Mar 17, 2014 at 09:33:58PM +0100, Gerhard Wiesinger wrote:
> > 
> > Hello Alexander,
> > 
> > I found the problem: Samba 4 behaves differently than Samba 3.6.x:
> > If "force user" is used in Samba 4 it must be also on the valid
> > users list. If not, access is denied.
> > In Samba 3.6.x this wasn't necessary.
> > 
> > NOK:
> >         valid users = @users
> >         force user = apache
> > OK:
> >         valid users = @users apache
> >         force user = apache
> > 
> > So this is either a bug or at least it should be documented as a
> > different behavior in Samba 4 (with a big explanation marks).
> 
> It's logged as bug:
> 
> https://bugzilla.samba.org/show_bug.cgi?id=9878
> 
> I may have just found a quick and easy fix for this.
> Testing right now...

And here it is ! Versions attached for 4.0.x and
4.1.x. Please test and let me know if this fixes
the issue, then I'll get these into master and
into the next Samba released versions.

Cheers,

	Jeremy.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug-9878-4.1.patch
Type: text/x-diff
Size: 2301 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140317/b2e9279f/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug-9878-4.0.patch
Type: text/x-diff
Size: 2329 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140317/b2e9279f/attachment-0001.patch>