Yikes! FreeBSD samba-3.0.26a_2,
1 is forbidden: "Remote Code Execution...
jerrymc at msu.edu
Fri Dec 14 09:39:24 PST 2007
On Fri, Dec 14, 2007 at 10:37:10AM -0600, W. D. wrote:
> At 09:50 12/12/2007, Remko Lodder wrote:
> >W. D. wrote:
> >>>> Dang! When will this be fixed?
> >>> Soon, there are patches available, we just need to make sure that it
> >>> doesn't bite anything while we are in a ports-slush, hence the FORBIDDEN
> >>> part.
> >>> Best regards,
> >>> Remko
> >> Hours? Days? Weeks?
> >The freebsd port will be up to date as soon as possible, there are fixes
> >available already on the Samba websites..
> >Best regards,
> 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?
I guess, if you are in a hurry, you are welcome to do the work.
It will get done as soon as the volunteers who maintain it get
to doing it. If you need it sooner, then get busy and do it
You won't assist them any by getting sarcastic and juvenile about it either.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions