From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Mar 30 02:10:01 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C25383B7 for ; Sat, 30 Mar 2013 02:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B39FC885 for ; Sat, 30 Mar 2013 02:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2U2A18h007551 for ; Sat, 30 Mar 2013 02:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2U2A1le007550; Sat, 30 Mar 2013 02:10:01 GMT (envelope-from gnats) Date: Sat, 30 Mar 2013 02:10:01 GMT Message-Id: <201303300210.r2U2A1le007550@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Darren Pilgrim Subject: Re: ports/177416: mail/postgrey has surfaced a bug in perl's taint checking X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Darren Pilgrim List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Mar 2013 02:10:01 -0000 The following reply was made to PR ports/177416; it has been noted by GNATS. From: Darren Pilgrim To: Paul Beard Cc: "bug-followup@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.