From owner-svn-src-head@FreeBSD.ORG Fri Aug 30 18:03:55 2013 Return-Path: Delivered-To: svn-src-head@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 144D9C3C; Fri, 30 Aug 2013 18:03:55 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [199.192.164.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E517925D3; Fri, 30 Aug 2013 18:03:54 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by m2.gritton.org (8.14.5/8.14.5) with ESMTP id r7UI3lCk046145; Fri, 30 Aug 2013 12:03:47 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <5220DE7D.5000806@FreeBSD.org> Date: Fri, 30 Aug 2013 12:03:41 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130807 Thunderbird/17.0.7 MIME-Version: 1.0 To: Jase Thew Subject: Re: svn commit: r252841 - in head/sys: dev/mem kern sys References: <201307052131.r65LVGKr089550@svn.freebsd.org> <5220D2D5.6030105@FreeBSD.org> In-Reply-To: <5220D2D5.6030105@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2013 18:03:55 -0000 On 08/30/13 11:13, Jase Thew wrote: > On 05/07/2013 22:31, Jamie Gritton wrote: >> Author: jamie >> Date: Fri Jul 5 21:31:16 2013 >> New Revision: 252841 >> URL: http://svnweb.freebsd.org/changeset/base/252841 >> >> Log: >> Add new privileges, PRIV_KMEM_READ and PRIV_KMEM_WRITE, used in >> opening >> /dev/kmem and /dev/mem (in addition to traditional file permission >> checks). >> PRIV_KMEM_READ is different from other PRIV_* checks in that it's >> allowed >> by default. >> >> Reviewed by: kib, mckusick >> > > Hi Jamie, > > As a result of this commit (and r252845), it is no longer possible to > access /dev/mem and /dev/kmem inside of a jail - is this behaviour > intentional? > > # dd if=/dev/mem bs=64 count=1 > dd: /dev/mem: Operation not permitted It's intentional, but it's not intended to be the full solution. I also need to add a permission flag to jails to allow kmem access. However I didn't intend to disrupt read permission, though clearly it does since it now passes through prison_priv_check. So I ought to add some code in prison_priv_check that mirrors the code in priv_check_cred to allow PRIV_KMEM_READ by default. - Jamie