What is blocking a Samba4 Tech Preview?
jelmer at samba.org
Mon Dec 19 01:00:35 GMT 2005
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
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?
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
- Bugzilla product (already appears to be there)
> > Certainly! The Debian packages of Samba4 are a bit more sane now,
> > after a couple of patches from Steinar Gunderson (Sesse for those on
> > IRC), so I hope we can get some Samba4 packages in Debians
> > experimental as well.
> I think source only is appropriate for a tech preview. Binary
> packaging issues are more important for a later release.
I agree, but since I've already put the effort in I might as well go
ahead with it.
Jelmer Vernooij <jelmer at samba.org> - http://jelmer.vernstok.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/samba-technical/attachments/20051219/ffa5681b/attachment.bin
More information about the samba-technical