[Proposal] Samba 3.2.0 to replace 3.0.22
abartlet at samba.org
Thu Jan 5 19:23:01 GMT 2006
On Thu, 2006-01-05 at 09:20 -0600, Gerald (Jerry) Carter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> * jerry steps up to the mic
> * tap, tap, tap
> * "Is this thing on?"
> I've been talking to Jeremy, Guenther, Volker, and some others
> about the upcoming changes currently in trunk. It seems that
> the patch pressure is getting quite high for the SAMBA_3_0 tree.
> If you haven't followed some of the discussion, here's some of
> the relevant threads:
> * [PATCH] kerberize pam_winbindd (work in progress)
> * "algorithmic rid base" bogus?
> * usershare acl parser?
> * [PATCH] Autogenerated DFS parser
Does the cluster work also fall into this?
> So the is major work in offline winbindd support, removing legacy
> rid algorithm support, non-root user creation of shares for desktop
> applications like KDE & Gnome, & backporting Samba 4's IDL upport.
> None of this is designed to compete or impeed Samba 4's development.
> In many ways it moves us closer to Samba 4's view of the future and
> is the product of continued, active development on Samba 3.0.x.
> However, these changes are really too sweeping to place in a 3.0.22
> or even a 3.0.30 release for that matter.
Personally, I would like to see some enhanced security defaults for
Samba 3.2. For example, a requirement for some form of integrity
protection on winbindd connections (either smb signing, NTLMSSP or
schannel pipes etc), and dropping of plaintext password support by
Also, if the Samba 3.2 thing is done, I would also like to see some more
Samba4 code pulled back. While pulling back GENSEC probably has too
many knobs on (have you seen how many places the credentials system has
it's little fingers in? :-), it would be good to see ldb pulled back.
> So the proposal on the table is to move to SAMBA_3_2. I realize
> the implications of this wrt to documentation, distributions,
> and developer resources. We would be looking at a turn around time
> of a few months. Hopefully by Samba XP, April 24, if not sooner.
> I propose skipping any 3.1.x releases in spite of past discussions
> due to the expected turnaround time and start with the 3.2.0preX
> releases as soon as the SAMBA_3_2 branch is feature complete.
> And we will continue with any necessary bug fix or security
> releases for 3.0.x. Bug fix releases being the 'letter' releases
> (3.0.21b, etc, ...) and security fixes eating a minor version
> number as usual.
This is the big cost, but perhaps we would have that anyway. We have
been fortunate in that we have not had security issues since doing
3.0.20, but I suspect that we would all feel a bit bad leaving anybody
on < 3.0.20 high and dry in the case of a security issue. So perhaps it
isn't a massive amount more work anyway. It depends how many 'bug
fixes' folks are tempted/demanded to spend their time on.
> * jerry opens the floor for discussion
It is really up to the Samba3 maintainers, but I certainly understand
the reluctance to change the behaviours radically in the 3.0 series.
That said, 3 product versions is a lot for this small team.
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/20060106/0ce839cd/attachment.bin
More information about the samba-technical