From owner-freebsd-security Fri Jun 18 12:37: 0 1999 Delivered-To: freebsd-security@freebsd.org Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (Postfix) with ESMTP id 8494814D7B for ; Fri, 18 Jun 1999 12:36:45 -0700 (PDT) (envelope-from synk@swcp.com) Received: (from synk@localhost) by kitsune.swcp.com (8.8.8/1.2.3) id NAA17158; Fri, 18 Jun 1999 13:36:23 -0600 (MDT) Date: Fri, 18 Jun 1999 13:36:23 -0600 (MDT) From: Brendan Conoboy Message-Id: <199906181936.NAA17158@kitsune.swcp.com> To: wes@softweyr.com Subject: Re: make world clobbers (was Re: some nice advice...) Cc: jgreco@ns.sol.net, security@FreeBSD.ORG Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Er, don't you upgrade from source when there's a security problem in > > userland but no new binary distribution? I do. > > Good grief, no! *IF* the bug is in a service that you are using, > you update the source, build and test the new service on an off-line > workstation or server, and when you're certain the changes are > reliable, move the new binaries to the target server. Oh, I see. We're having a semantical difficulty. I would still call that upgrading from source. I thought the original poster meant that one ought to to wait for 3.2-release to come out when there was a serious bug in 3.1, to essentially leave the source out of it. -Brendan (synk@swcp.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message