Date: Sat, 30 Mar 2013 01:30:01 GMT From: Paul Beard <paulbeard@gmail.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Message-ID: <201303300130.r2U1U1Cq000592@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/177416; it has been noted by GNATS. From: Paul Beard <paulbeard@gmail.com> To: Darren Pilgrim <ports.maintainer@evilphi.com> Cc: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org> Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking Date: Fri, 29 Mar 2013 18:21:36 -0700 OK, with just these perl modules installed:=20 /var/db/pkg/p5-BerkeleyDB-0.51: /var/db/pkg/p5-Digest-HMAC-1.03: /var/db/pkg/p5-IO-Multiplex-1.13: /var/db/pkg/p5-IO-Socket-INET6-2.69: /var/db/pkg/p5-IO-stringy-2.110: /var/db/pkg/p5-Net-DNS-0.72: /var/db/pkg/p5-Net-Server-2.007: /var/db/pkg/p5-Parse-Syslog-1.10: /var/db/pkg/p5-Socket6-0.23: postgrey does what it should.=20 But as you might imagine, that's not really very useful. I suppose the = best way to unearth the bug is to install all the old ports, one at a = time, and check to see if/when postgrey loses its mind again.=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303300130.r2U1U1Cq000592>