From owner-freebsd-arch@freebsd.org Sun Nov 29 15:41:39 2020 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ECDC24A5CB1; Sun, 29 Nov 2020 15:41:39 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CkXfC6Dt5z4mf6; Sun, 29 Nov 2020 15:41:39 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id AEF7124177; Sun, 29 Nov 2020 15:41:39 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id A61058D4A166; Sun, 29 Nov 2020 15:41:38 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 273DEE707C7; Sun, 29 Nov 2020 15:41:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id mvFUICsQe4UG; Sun, 29 Nov 2020 15:41:37 +0000 (UTC) Received: from [127.0.0.1] (unknown [IPv6:fde9:577b:c1a9:4902:20d4:cd87:918b:4dde]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id B69CCE707C2; Sun, 29 Nov 2020 15:41:36 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Kyle Evans" Cc: "James Gritton" , freebsd-jail , freebsd-arch@freebsd.org, trustedbsd-discuss@freebsd.org Subject: Re: RFC: Jail privsets Date: Sun, 29 Nov 2020 15:41:36 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: In-Reply-To: References: <06F654BB-B087-4AE5-8599-E5837A85A850@FreeBSD.org> <6BA03DAD-BDCD-4A53-A80A-4B7B476B803C@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2020 15:41:40 -0000 On 29 Nov 2020, at 15:33, Kyle Evans wrote: > Sure- I'm not so sure about vnet, but all of the allow flags could get > deprecated in favor of describing the privs available somewhere and > letting admin make decisions. I think the vnet set still makes a lot > of sense unless you're also proposing that we could just create new > vnets if one of those privileges is turned on -- in which case, we'd > still have to manage the set, but it wouldn't be used much beyond a > hint mask that we need to create a vnet. What I am thinking of is a /etc/defaults/devfs.rules a-like set of privs describing base, jail, jailvnet and then pick appropriately if the jail gets created with vnet (though I can imagine some people extending a default jail set — e.g. for raw sockets — or removing some privs from a vnet jail set). The tricky bit would be to manage the header file and the text description, but having a default wildcard of “*” or “all” for base would probably catch the most cases. /bz