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

[Paul Beard]

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

From: Paul Beard <paulbeard at gmail.com>
To: Darren Pilgrim <ports.maintainer at evilphi.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: Wed, 3 Apr 2013 09:05:26 -0700

 So this is resolved, as best I can tell with no inbound smtp to check it =
 with. I never determined what port was the issue.=20
 
 My count of p5 ports is down to 54. Everything seems to work. I did hit =
 an error on a portmaster run where the port had some traces of CVSup =
 which got me a string of warning messages. I haven't used CVSup in quite =
 some time. So there's probably more of that out there waiting to be =
 tripped over.=20
 
 Are there any existing scripts or tools that review installed ports, =
 other than libchk and pkg_check? What I take away from this is that I =
 should be prepared to rip out every perl module and then reinstall all =
 the leaf ports, just to make sure there are no collisions. So in the =
 event perl5.16 becomes the default, I may do that.=20
 
 I never did find out why there is a p5-IO  port installed alongside the =
 same named port in the base perl install. That was part of the issue, =
 that postgrey was using trying to use it based on the name. But I never =
 worked out uninstalling it and rebuilding perl didn't solve it. Or how =
 it kept coming back with 4 year old timestamps.=20
 
 
 
 
 --
 Paul Beard
 
 Are you trying to win an argument or solve a problem?=20