Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Sep 2014 16:02:24 +0100
From:      Matthew Seaman <matthew@freebsd.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Bash Shellshock Bug
Message-ID:  <542AC600.1090600@freebsd.org>
In-Reply-To: <20140930152801.cd7a2a5e.freebsd@edvax.de>
References:  <OFBBD12885.C6A08B7B-ON65257D63.002E6EFF-CA257D63.002F0BCD@in.ibm.com> <20140930110034.a637ab6d.freebsd@edvax.de> <OFC03B0588.4C96789C-ON65257D63.00324F6D-CA257D63.0032A7E5@in.ibm.com> <20140930152801.cd7a2a5e.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--nAuWlbGLFb4pBJXkoijSbU2LkeA50oVgV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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...
>=20
> This is how you would do it:
>=20
> 	# portsnap fetch update
> 	# cd /usr/ports/shells/bash
> 	# make deinstall
> 	# make
> 	# make reinstall
>=20
> 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:
>=20
> 	# 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.=


Nor will the current ports tree work with anything other than pkg(8).
We haven't tried compiling pkg(8) on anything that old -- it might work,
but I sincerely doubt it.

	Cheers,

	Matthew





--nAuWlbGLFb4pBJXkoijSbU2LkeA50oVgV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJUKsYTXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw
MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnQDYQAIcuRxXDpfhDTKRFofUd8Ygf
zuoK9ZDVGdhX8wUREVnCTN02YNWBWaALtBQYivd5/4toS8vVk/Wn11nMVmSe35xB
HheB9zuEpU7/Jm4j1UtBysQzY1JYM5xPpULB0FYevDUjbifVdMLUuu22bFVoUXvn
ShV8rmvC/A3EifBx1pTdr4XLPuxX966blYiRXFT35i3cWNQWSta87cLhb4Gq68TQ
aeXh9AcRO5ACuAMM0W/WIELNU04f6IP1ZXNHfBOMBkKVzcHpXcvMBSplEqwTGO3A
pLItpmFNHtZApz5jtSMMgBdEDK3ExC1+n54FVOB7koK0mt8CHWkvo42w3uWjCwGl
as293iUDRIf3D8uR8Y1RaiMdUI5Dnji3Fcpr2KwOzGEF5alIGAHY+9zNGyxjLVkx
PgSSc9B32IeqlcW46nUr3WGejFgHjbem80hVjoiz4IaAQTnIA66hdt4mC7Cy8HQn
auMS1m2LTUIfkBvCsYgLJ73QTwdffYTwBcEfdObZOXDVeBOJ7GSPOJzP2qCjIvCs
X0M7dAGmTDBMrzewnbJsMHVRboQjsKPp4umnt9coysPmo70tW8nc0QjAaNGRCDIW
n0iz6Ctc5o6OLosyjfJPrTb7n216LqYAiyEJivR9FzhFaJcJX0W5POUBfkN2xOoS
09IHZXenECy3DLAqV0/w
=cy7E
-----END PGP SIGNATURE-----

--nAuWlbGLFb4pBJXkoijSbU2LkeA50oVgV--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?542AC600.1090600>