Date: Mon, 28 Feb 2005 16:55:55 +1030 From: Ian Moore <no-spam@swiftdsl.com.au> To: Jacques Vidrine <nectar@freebsd.org> Cc: security@freebsd.org Subject: Re: linux-tiff port update Message-ID: <200502281656.03547.no-spam@swiftdsl.com.au> In-Reply-To: <4222939A.9070808@FreeBSD.org> References: <200502191157.06108.no-spam@swiftdsl.com.au> <20050226151113.00ec3099@Magellan.Leidinger.net> <4222939A.9070808@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3373443.pHIpO94GyZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 28 Feb 2005 14:14, Jacques Vidrine wrote: > On 2/26/05 8:11 AM, Alexander Leidinger wrote: > > Hello security team, is this an error in the vuln.xml document or is the > > commit log of the port-Makefile misleading > > It's our bad. It looks like we mistakenly believed the FreeBSD package > version numbers were aligned between tiff and linux-tiff. > > > (and Suse is still > > vulnerable, since they don't offer newer packages)? > > No, these issues are fixed in those packages. > > Cheers, So does that mean I should be able to upgrade from linux-tiff-3.5.5_2 to=20 linux-tiff-3.6.1_1 without the security vunerabilty warning now? (Because I= =20 still the warnings) Cheers, =2D-=20 Ian GPG Key: http://home.swiftdsl.com.au/~imoore/no-spam.asc --nextPart3373443.pHIpO94GyZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCIrl7PUlnmbKkJ6ARAjJ5AJ4j3Zv1vdSUppdIn44+hXS9cqSOLgCdFSpt l69xT/qfmoqz9EmeNYN5GQI= =NmSC -----END PGP SIGNATURE----- --nextPart3373443.pHIpO94GyZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502281656.03547.no-spam>