According to
https://www.freebsd.org/security/advisories/FreeBSD-SA-14:19.tcp.asc
the workaround is to turn on pf.
Therefore, the answer to your question is technically yes but in
practice no.
On Thu, Sep 18, 2014 at 8:55 AM, Martin Fuchs mar...@fuchs-kiel.de wrote:
Hi !
Does CVE-2004-0230
sounds reasonable ;-)
thanks a lot,
martin
Date: Thu, 18 Sep 2014 09:03:16 -0400
From: vi...@khera.org
To: list@lists.pfsense.org
Subject: Re: [pfSense] CVE-2004-0230
According to
https://www.freebsd.org/security/advisories/FreeBSD-SA-14:19.tcp.asc
the workaround is to turn on pf
On 9/18/2014 8:55 AM, Martin Fuchs wrote:
Does CVE-2004-0230 affect pfSense 2.1.5 ?
As Vick mentions, practically the answer is 'no'.
There are some rare cases when it might, however. It would require:
1. Disabled pf (System Advanced, Firewall/NAT tab, check Disable all
packet filtering)
1a.
Maybe a blog post about this?
-- Jim
On Sep 18, 2014, at 10:01, Jim Pingle li...@pingle.org wrote:
On 9/18/2014 8:55 AM, Martin Fuchs wrote:
Does CVE-2004-0230 affect pfSense 2.1.5 ?
As Vick mentions, practically the answer is 'no'.
There are some rare cases when it might, however. It
