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

Fri Mar 29 06:10:01 UTC 2013

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: Thu, 28 Mar 2013 23:08:22 -0700

 --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D
 Content-Type: text/plain;
 	charset=us-ascii
 Content-Transfer-Encoding: quoted-printable

 On Mar 28, 2013, at 10:20 PM, Darren Pilgrim <ports.maintainer at evilphi.com> w=
 rote:

 > There are steps between what's been done so far and a brand new system.  A=
  complete refetch and reinstall of everything perl is one such step.
 >=20

 Done. Still seeing it.=20
 >=20
 > That's more or less my point, yes.  You have about 5 times as many p5 port=
 s as I've ever seen on one system.
 >=20
 Hey, I don't ask for them, they're mostly dependencies called by other ports=
 . I could try removing them all and just installing postgrey and it's depend=
 encies but that never came up before now.=20

 >=20
 > The thing is I can't reproduce this behaviour.  I even ran it on a RELENG_=
 6 system and it worked fine there.

 And it worked fine here until, suspiciously, I lost port 25 service. Coincid=
 ence, I'm sure, but that's when I noticed it.=20

 >=20
 > But it's a PR for the mail/postgrey port.  It sounds like it's reasonable t=
 o close this PR.

 I have no idea what piece of code is balking, I just know what provokes it. H=
 ence the wording: "mail/postgrey has surfaced a bug in perl's taint checking=
 ."=20

 So close it. I was optimistic that filing a PR might get more than one pair o=
 f eyes looking at it, especially as the error wasn't in the port with which t=
 hey were associated.=20=

 --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D
 Content-Type: text/html;
 	charset=utf-8
 Content-Transfer-Encoding: quoted-printable

 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
 utf-8"></head><body dir=3D"auto"><div><br></div><div><br>On Mar 28, 2013, at=
  10:20 PM, Darren Pilgrim <<a href=3D"mailto:ports.maintainer at evilphi.com=
 ">ports.maintainer at evilphi.com</a>> wrote:<br><br></div><blockquote type=3D=
 "cite"><span>There are steps between what's been done so far and a brand new=
  system.  A complete refetch and reinstall of everything perl is one su=
 ch step.</span><br><span></span><br></blockquote><div><br></div><div>Done. S=
 till seeing it. </div><blockquote type=3D"cite"><blockquote type=3D"cit=
 e"><div style=3D"display: none; "><br></div></blockquote><span></span><br><s=
 pan>That's more or less my point, yes.  You have about 5 times as many p=
 5 ports as I've ever seen on one system.</span><br><span></span><br></blockq=
 uote>Hey, I don't ask for them, they're mostly dependencies called by other p=
 orts. I could try removing them all and just installing postgrey and it's de=
 pendencies but that never came up before now. <div><div><br><blockquote=
  type=3D"cite"><blockquote type=3D"cite"><div style=3D"display: none; "><br>=
 </div></blockquote><span></span><br><span>The thing is I can't reproduce thi=
 s behaviour.  I even ran it on a RELENG_6 system and it worked fine the=
 re.</span><br></blockquote><div><br></div>And it worked fine here until, sus=
 piciously, I lost port 25 service. Coincidence, I'm sure, but that's when I n=
 oticed it. </div><div><br><blockquote type=3D"cite"><blockquote type=3D=
 "cite"><div style=3D"display: none; "><br></div></blockquote><span></span><b=
 r><span>But it's a PR for the mail/postgrey port.  It sounds like it's r=
 easonable to close this PR.</span><br></blockquote><div><br></div>I have no i=
 dea what piece of code is balking, I just know what provokes it. Hence the w=
 ording: "<span style=3D"font-family: '.HelveticaNeueUI'; font-size: 15px; li=
 ne-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 2=
 6, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.2304=
 69); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-=
 text-size-adjust: none; ">mail/postgrey has surfaced a bug in perl's taint c=
 hecking." </span><br><br></div><div>So close it. I was optimistic that f=
 iling a PR might get more than one pair of eyes looking at it, especially as=
  the error wasn't in the port with which they were associated. </div></=
 div></body></html>=

 --Apple-Mail-BBBDAB24-12EB-4514-B60A-24C860CE312D--