ports/177416: mail/postgrey has surfaced a bug in perl's taint checking

[Darren Pilgrim]

The following reply was made to PR ports/177416; it has been noted by GNATS.

From: Darren Pilgrim <ports.maintainer at evilphi.com>
To: Paul Beard <paulbeard at gmail.com>
Cc: "bug-followup at FreeBSD.org" <bug-followup at FreeBSD.org>
Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint
 checking
Date: Fri, 29 Mar 2013 19:01:46 -0700

 On 2013-03-29 18:21, Paul Beard wrote:
  > OK, with just these perl modules installed:
  > /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.
 
 I'm glad you got it working!
 
 > 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.
 
 Yes, that would be the only way to know for sure which module is the 
 culprit.  It's time-intensive, but it would be worth it to hunt down the 
 stale perl module.  You could install them in dependency groups.  At 
 least that way you can pare it down to a handful for which you must test 
 one by one, instead of all 600.