From owner-freebsd-ports@FreeBSD.ORG Thu Apr 23 14:17:48 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE1551065672; Thu, 23 Apr 2009 14:17:48 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 608F48FC24; Thu, 23 Apr 2009 14:17:48 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id D0BED5C17; Thu, 23 Apr 2009 10:17:47 -0400 (EDT) Date: Thu, 23 Apr 2009 10:17:47 -0400 From: Wesley Shields To: Pavel Hlub?k Message-ID: <20090423141747.GD37379@atarininja.org> References: <20090423131212.GB37379@atarininja.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090423131212.GB37379@atarininja.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: mnag@FreeBSD.org, ports@FreeBSD.org Subject: Re: FreeBSD Port: libspf2-1.0.4_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 14:17:49 -0000 On Thu, Apr 23, 2009 at 09:12:12AM -0400, Wesley Shields wrote: > On Thu, Apr 23, 2009 at 11:44:31AM +0200, Pavel Hlub?k wrote: > > Hi , > > > > sorry for disturbing you. > > > > The port is still broken so I can't install the `postfix-policyd-spf` > > because it depends on the libspf2-10. > > > > ===> libspf2-1.0.4_1 has known vulnerabilities: > > => libspf2 -- Buffer overflow. > > Reference: > > > .html> > > > > I want to use a ports system because it is easier using a `portupgade` to > > upgrade the application in the future. > > Can you write me when the problem can be solved. Thank you very much. > > > > I run FreeBSD 7.1-RELEASE-p4. > > It looks like the master site is no longer valid. A quick google search > didn't show up any other updated locations. Can you move to libspf2? My apologies, I was looking at mail/libspf and not mail/libspf2-10. I'm not sure if mail/postfix-policyd-spf will work with mail/libspf2. I'd try changing the lib dependency to be looking for spf2.3 instead and see if it works. > I think this port should be retired as it appears abandoned upstream. This part still holds true as it appears mail/libspf has been abandoned upstream. -- WXS