On 28 August 2011 11:35, Uffe R. B. Andersen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Den 28-08-2011 02:00, Doug Barton skrev:
>> I appreciate your responses, but I think you're missing one or
>> more large'ish pieces of the puzzle. Here is what I'm seeing with
>> an up to date
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Den 28-08-2011 02:00, Doug Barton skrev:
> I appreciate your responses, but I think you're missing one or
> more large'ish pieces of the puzzle. Here is what I'm seeing with
> an up to date portaudit db:
>
> portaudit -a Affected package: libspf2-1.0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/27/2011 15:36, Uffe R. B. Andersen wrote:
> Den 27-08-2011 23:05, Doug Barton skrev:
>>> libspf2 port is currently libspf2-1.2.9_1 and according to the
>>> page you refer to, the vulnerability affects libspf2 <1.2.8.
>
>> Yes, that was my poin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Den 27-08-2011 23:05, Doug Barton skrev:
>> libspf2 port is currently libspf2-1.2.9_1 and according to the
>> page you refer to, the vulnerability affects libspf2 <1.2.8.
>
> Yes, that was my point. :) mail/libspf2-10 and mail/libspf2 are
> differen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/27/2011 11:07, Uffe R. B. Andersen wrote:
> Den 26-08-2011 22:22, Doug Barton skrev:
>> Howdy,
>
>> Doing some port updates and noticed that mail/postfix-policyd-spf
>> relies on mail/libspf2-10, which according to
>> http://portaudit.FreeBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Den 26-08-2011 22:22, Doug Barton skrev:
> Howdy,
>
> Doing some port updates and noticed that mail/postfix-policyd-spf
> relies on mail/libspf2-10, which according to
> http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e16.html
>
>
is v
Howdy,
Doing some port updates and noticed that mail/postfix-policyd-spf relies
on mail/libspf2-10, which according to
http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e16.html
is vulnerable. There is a port of mail/libspf2 which is not vulnerable,
is it possible to update mail/postfi
