From owner-freebsd-questions@FreeBSD.ORG  Mon Sep 29 15:23:39 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 94DDCCE0
 for <questions@freebsd.org>; Mon, 29 Sep 2014 15:23:39 +0000 (UTC)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.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 56B33A64
 for <questions@freebsd.org>; Mon, 29 Sep 2014 15:23:38 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-99-5.dynamic.qsc.de [92.195.99.5])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 5AFBB2766E;
 Mon, 29 Sep 2014 17:23:30 +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 s8TFNTrB002144;
 Mon, 29 Sep 2014 17:23:29 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Mon, 29 Sep 2014 17:23:29 +0200
From: Polytropon <freebsd@edvax.de>
To: Shane Ambler <FreeBSD@ShaneWare.Biz>
Subject: Re: BASH Shellshock and FreeBSD 4.X
Message-Id: <20140929172329.08163a41.freebsd@edvax.de>
In-Reply-To: <5429579A.7030501@ShaneWare.Biz>
References: <CAFBwhDY-dmS476OPWEBnj=TtywDQnCA8scOEmWdoxQwB_KNb6g@mail.gmail.com>
 <20140929100937.0527cbae.freebsd@edvax.de>
 <5429579A.7030501@ShaneWare.Biz>
Reply-To: Polytropon <freebsd@edvax.de>
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: Questions at FreeBSD <questions@freebsd.org>,
 Everett Batey <efbatey@gmail.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 15:23:39 -0000

On Mon, 29 Sep 2014 22:29:06 +0930, Shane Ambler wrote:
> On 29/09/2014 17:39, Polytropon wrote:
> > On Sun, 28 Sep 2014 13:59:13 -0700, Everett Batey wrote:
> >> Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash
> >> risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT
> >> escape ..
> 
> > If you're using ports:
> > 
> > 	# portsnap fetch update
> > 	# cd /usr/ports/shells/bash
> > 	# make deinstall
> > 	# make
> > 	# make reinstall
> > 
> 
> I'm not 100% certain that the current ports tree will work on 4.x
> 
> I'd keep a copy of your current tree before trying updates. If you have
> trouble with the current ports then put the old version back in place
> and look at the changes made to fix the issue and incorporate them into
> your tree.

Yes, _that_ might be a problem...

On the other hand, maybe it would even be possible to check
out the current source for bssh (and maybe its dependencies)
and build them "off the track", i. e., not using the ports
infrastructure at all, and then manually copying the resulting
binary to the required place, as well as its libraries (unless
static linking has been enabled). It's worth having a look at
./configure's options to tune this approach.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...