What is blocking a Samba4 Tech Preview?
abartlet at samba.org
Sun Dec 18 06:15:41 GMT 2005
As the release cycle for Samba4 drags on, it has been put to me that if
we don't start making releases, we never will.
So, I'm wondering what issues actually get in the way of a Samba4 tech
I see the following:
- Win2000 Kerberos support
- Simple Binds in the LDAP server
- Fixed ACLs in LDB
- Fixed ACLs in the registry
- Documented add/delete/set user (even if just assistance with ldbedit)
- Samba3 member support (at least partial)
Things I don't see on the list for a first Domain Controller tech
- Winbindd complete
- Domain member support
- Dynamic ACLs
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.
If we can get some of this code out into the hands of users, we might
get the interest and developers we so desperately need, but doing
'nothing' (ie continuing development) isn't going to move us.
We have some very good code in Samba4 now, and our users deserve to see
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
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20051217/35037cc9/attachment.bin
More information about the samba-technical