What is blocking a Samba4 Tech Preview?

[Andrew Bartlett]

On Mon, 2005-12-19 at 02:00 +0100, Jelmer Vernooij wrote:
> On Mon, Dec 19, 2005 at 08:43:34AM +1100, tridge at samba.org wrote about 'Re: What is blocking a Samba4 Tech Preview?':
> >  > > In the ACL space I don't think that the current (very valuable) work
> >  > > tridge is doing should block the release of the code.  Instead we should
> >  > > hard-code the same 'admin write, others read' ACL that Samba3 has.  
> >  > That's a sane alternative, indeed. 
> > yep, and then when the ldb ACLs are working we can do an updated
> > release.
> What exactly would be necessary for such a hardcoded ACL? I'm
> afraid I'm not really sure what kind of architecture we're planning to
> use for authorization. Security tokens or something similar? 

We already push a session_info into LDB.  I'm not sure the js is right,
but the basics are there for the rest of smbd.  The SID list in that can
be checked against the hard-coded ACL.

> Some other (meta?) things I think we need for a TP release:
> 
> - The current HOWTO doesn't yet mention SWAT, perhaps other important 
>   things as well
> - A list of features that should work and features that don't yet work 
>   would be useful
> - Some sort of introduction and explanation of change in architecture
>   wrt Samba 3, details on where we are (what is a technology
>   preview?) and instructions for bug reports / wishlist items

These sound good.

> - Bugzilla product (already appears to be there)

It probably needs more than me looking at the bugs, but it's there.

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Student Network Administrator, Hawker College  http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20051218/e16938f5/attachment.bin