From owner-freebsd-questions@FreeBSD.ORG Fri Dec 14 17:39:24 2007 Return-Path: Delivered-To: FreeBSD-Questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9D0216A420 for ; Fri, 14 Dec 2007 17:39:24 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 6541B13C46E for ; Fri, 14 Dec 2007 17:39:24 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id lBEHcoKS022064; Fri, 14 Dec 2007 12:38:50 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id lBEHcovm022063; Fri, 14 Dec 2007 12:38:50 -0500 (EST) (envelope-from jerrymc) Date: Fri, 14 Dec 2007 12:38:50 -0500 From: Jerry McAllister To: "W. D." Message-ID: <20071214173850.GA22045@gizmo.acns.msu.edu> References: <20071212065822.4F6A313C457@mx1.freebsd.org> <475F9560.40703@FreeBSD.org> <20071212090407.8B26613C478@mx1.freebsd.org> <47600358.3010909@FreeBSD.org> <20071214164358.5D01A13C461@mx1.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071214164358.5D01A13C461@mx1.freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: samba@lists.samba.org, Remko Lodder , Timur@freebsd.org, FreeBSD-Questions@freebsd.org Subject: Re: Yikes! FreeBSD samba-3.0.26a_2, 1 is forbidden: "Remote Code Execution... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2007 17:39:24 -0000 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, > >remko > > 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 yourself. You won't assist them any by getting sarcastic and juvenile about it either. ////jerry > > > > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >