From owner-freebsd-stable Wed Nov 1 10:42: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 926D837B4F9 for ; Wed, 1 Nov 2000 10:42:05 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA1Ihvm21041; Wed, 1 Nov 2000 10:43:57 -0800 (PST) (envelope-from kris) Date: Wed, 1 Nov 2000 10:43:57 -0800 From: Kris Kennaway To: Christian Ruediger Bahls Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FW: Pine 4.30 now available (fwd) Message-ID: <20001101104357.A21000@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from christian@it-netservice.de on Wed, Nov 01, 2000 at 05:26:12PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Nov 01, 2000 at 05:26:12PM +0100, Christian Ruediger Bahls wrote: > is it still possible to merge the > new version of pine into > the ports-tree of 4.2-RELEASE ? Maybe..however unless they have silently fixed other things, the current port also fixes the known vulnerability, so running the FreeBSD pine-4.21_1 port shouldn't give you any more of an uneasy feeling than running pine in the first place should :-) Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoAZG0ACgkQWry0BWjoQKUzqwCghRnvlC5E8xpmxNc5I/0wXZo8 /b4AoLSY43Wj5o9pn4G02sBPxFNEGBOu =Zsya -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message