From owner-freebsd-questions@FreeBSD.ORG Tue Sep 30 17:44:45 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 074A0546; Tue, 30 Sep 2014 17:44:45 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD4E5F6F; Tue, 30 Sep 2014 17:44:44 +0000 (UTC) Received: from r56.edvax.de (port-92-195-75-189.dynamic.qsc.de [92.195.75.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 40DC13CD64; Tue, 30 Sep 2014 19:44:40 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s8UHieiK002068; Tue, 30 Sep 2014 19:44:40 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 30 Sep 2014 19:44:40 +0200 From: Polytropon To: Matthew Seaman Subject: Re: Bash Shellshock Bug Message-Id: <20140930194440.5f2cdb44.freebsd@edvax.de> In-Reply-To: <542AC600.1090600@freebsd.org> References: <20140930110034.a637ab6d.freebsd@edvax.de> <20140930152801.cd7a2a5e.freebsd@edvax.de> <542AC600.1090600@freebsd.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 17:44:45 -0000 On Tue, 30 Sep 2014 16:02:24 +0100, Matthew Seaman wrote: > On 09/30/14 14:28, Polytropon wrote: > > Again note: Make a backup (!) of your current /usr/ports > > tree before you start! Updating the ports tree is possible, > > but probably you don't even have portsnap on FreeBSD 6 yet. > > I'm not sure when it has been introduced, but I assume it > > was somewhere betweeen FreeBSD 7 and 8... > > > > This is how you would do it: > > > > # portsnap fetch update > > # cd /usr/ports/shells/bash > > # make deinstall > > # make > > # make reinstall > > > > If you have any other means to update your ports tree (CVS > > was the standard at FreeBSD 6, I don't know if this is still > > supported, as FreeBSD now uses Subversion), you could also > > try the equivalent with binary packages: > > > > # portsnap fetch update > > # portupgrade -P bash > > > Neither of these approaches will work with the current ports tree on > anything older than FreeBSD 8.2-RELEASE. You'll get syntax errors while > trying to parse the Makefiles used in the ports certainly because of a > change in the way you tell make to map strings to upper or lower case > (eg. ${VAR:L} changed to ${VAR:tl}) and quite possibly for other reasons. That was my initial fear - the ports infrastructure has changed in a way that it probably won't work on older versions. Thanks for confirming this fear. So working with the ports tree is out of scope, and probably there won't be most recent binary packages (for use with pkg_add) available... So it seems that building from source "off the track" might be the only solution here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...