From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 3 19:23:52 2014 Return-Path: Delivered-To: hackers@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 ESMTPS id 0E703F4 for ; Thu, 3 Jul 2014 19:23:52 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D59912B82 for ; Thu, 3 Jul 2014 19:23:51 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-250-191.lns20.per2.internode.on.net [121.45.250.191]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id s63JNltn033615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 3 Jul 2014 12:23:50 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <53B5ADBE.1020905@freebsd.org> Date: Fri, 04 Jul 2014 03:23:42 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Dautenhahn, Nathan Daniel" Subject: Re: Kernel Privilege Separation Policy References: <100A360A-DF5E-46D5-83F0-BCAE672D1D6C@illinois.edu> In-Reply-To: <100A360A-DF5E-46D5-83F0-BCAE672D1D6C@illinois.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2014 19:23:52 -0000 On 7/2/14, 10:52 PM, Dautenhahn, Nathan Daniel wrote: > Hi All- > > I am a graduate student at UIUC and am currently working on a system that > isolates the MMU from the rest of the FreeBSD kernel. For the purpose of > enabling privilege separtion within the kernel. > > [...] it does sound interesting.. I think the dearth of answers is that everyone is waiting for someone-else to answer, because the topic sounds a bit intimidating,