Yikes! FreeBSD samba-3.0.26a_2, 1 is forbidden: "Remote Code Execution...

[Paul Procacci]

> Well, it's been 2 days now.  When will the code be updated
> in the FreeBSD ports?  The version on the Samba website is
> 3.0.28.  (http://www.Samba.org/)  Why is the FreeBSD ports
> version stuck at 3.0.26a_2,1?
> 
> If there are fixes available already on the Samba websites,
> why can't they be integrated into the ports?
> 
> I neet to get a fileserver going right away.  I would like
> to use Samba.  Perhaps I should just load Windows on it?
> 
> It seems to me that leaving a port broken like this is
> very "unprofessional".  I would expect more from the folks
> maintaing FreeBSD.
> 
> When is it going to be fixed?  Does "soon" mean this century?
> This year?  When?

Would you like to give the maintainer some money to hurry your
absolute and urgent need?

This has been said more than enough times, but people have jobs
that actually make them money, and henceforth their priority.

Resorting to negative comments doesn't make the testing phase of
an updated port go any faster.

> I neet to get a fileserver going right away.  I would like
> to use Samba.  Perhaps I should just load Windows on it?

How about working with the maintainer, testing patches, and helping
with the port?  That certainly would be more beneficial to the
community.

;P

~Paul