Date: Mon, 29 Sep 2014 17:23:29 +0200 From: Polytropon <freebsd@edvax.de> To: Shane Ambler <FreeBSD@ShaneWare.Biz> Cc: Questions at FreeBSD <questions@freebsd.org>, Everett Batey <efbatey@gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140929172329.08163a41.freebsd>