From owner-freebsd-security@FreeBSD.ORG  Fri Sep 13 07:27:30 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 057F73CB
 for <freebsd-security@freebsd.org>; Fri, 13 Sep 2013 07:27:30 +0000 (UTC)
 (envelope-from dan@obluda.cz)
Received: from fw.ax.cz (fw.ax.cz [IPv6:2a00:1aa8:1:1000::2])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 817BC2CBB
 for <freebsd-security@freebsd.org>; Fri, 13 Sep 2013 07:27:28 +0000 (UTC)
Received: from [127.0.0.1] (host10.hide.ax.cz [172.20.1.29])
 by fw.ax.cz (8.14.5/8.14.5) with ESMTP id r8D7Qkct079338;
 Fri, 13 Sep 2013 09:26:47 +0200 (CEST) (envelope-from dan@obluda.cz)
Message-ID: <5232BE53.4040900@obluda.cz>
Date: Fri, 13 Sep 2013 09:27:15 +0200
From: Dan Lukes <dan@obluda.cz>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: Jonathon Wright <jonathon.s.wright@gmail.com>
Subject: Re: FreeBSD Transient Memory problem?
References: <CAGX1DMbQP=TggYQm-3hra0Od3gjgz5xQ8bEMMrueuhL6kuZMUA@mail.gmail.com>
 <20130912053559.GF68682@funkthat.com>
 <979901F9-5F25-4DF1-95A8-32473C55B25F@gmail.com>
 <52320144.2090807@freebsd.org>
 <CAGX1DMYAheUAV_eB4Z4R_YaMDx_LzrepEag5KyBC=EOxzhUiMQ@mail.gmail.com>
 <EC4378DB-3AF0-40F7-98BC-0FE6D318938E@gmail.com>
 <CAGX1DMY=bSpOkzHT=4mYVfSb_tUR6TVTwZqnUcNM-ORa-GBsRg@mail.gmail.com>
 <201309130040.SAA28208@mail.lariat.net>
 <CAGX1DMaONPyJ=5yiu+FGxa6Q_9WK4hzht7MF5K2+CzMWrpfYbg@mail.gmail.com>
 <CA+7WWScZB2UE9zM10YGMSGS4t1dat2CN5Eb3BDxKMZbWEFTz5A@mail.gmail.com>
In-Reply-To: <CA+7WWScZB2UE9zM10YGMSGS4t1dat2CN5Eb3BDxKMZbWEFTz5A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130912-1, 12.09.2013), Outbound message
X-Antivirus-Status: Clean
Cc: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Sep 2013 07:27:30 -0000

Kimmo Paasiala wrote:
>> While the NIAP Web site does not list FreeBSD as a "compliant"
>>> operating system product, it lists Juniper routers, which run an
>>> embedded version of FreeBSD, as compliant. See

> Unfortunately that might just mean that the company behind Juniper has
> payed enough money to get their product certified while basic FreeBSD
> remains uncertified.

Sure. But there are other aspects as well.

Juniper's FreeBSD has been verified (whatever it mean in such particular
case) as installed inside such router - e.g. version, patch level,
kernel compilation options,  loaded kernel modules,  ...

In short, results of security audit of FreeBSD 9.1-R-p2 compiled without
if_re module is not applicable to FreeBSD 9.1-R-p3 compiled with if_re
module nor to FreeBSD 9.1-R-p3 compiled without if_re module

Dan