The FreeBSD advisory says one has to upgrade to 7.0-RELEASE-p6 to get he bug fixed. pfSense 1.2.1-RC4 image I have downloaded couple days ago says it runs 7.0-RELEASE-p5.
Do you mean this flaw was fixed in the source tree of pfSense, independently from FreeBSD? I wonder if this fact was mentioned in some release notes or changelog document? I am doing a security review of a custom firewall based on pfSense and would like to have some official pfSense document to refer to. I can refer to this thread in the maillist I guess, but it is somewhat wierd ;). Kind regards, Alex Chris Buechler wrote: > On Wed, Dec 17, 2008 at 10:52 AM, a800 <[email protected]> wrote: > >> Hello, >> >> I would like to know how the last FreeBSD security advisory >> http://security.freebsd.org/advisories/FreeBSD-SA-08:11.arc4random.asc >> affects pfSense. I understand it is not fixed in 1.2.1-RC4. >> >> > > It's been fixed in every 1.2.1 snapshot since that was released, > including the RC2, 3 and 4 releases. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > Commercial support available - https://portal.pfsense.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
