From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A107DC2D0C2 for ; Mon, 30 Dec 2019 19:30:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 777242071E for ; Mon, 30 Dec 2019 19:30:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="A2huiwkM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727278AbfL3TaW (ORCPT ); Mon, 30 Dec 2019 14:30:22 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:46215 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727648AbfL3TaW (ORCPT ); Mon, 30 Dec 2019 14:30:22 -0500 Received: by mail-ot1-f66.google.com with SMTP id k8so30245037otl.13 for ; Mon, 30 Dec 2019 11:30:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=FWVYjFfIIe+qY04H734qWucJ1T7JU5SJXMfcm3nyZe8=; b=A2huiwkMJ6SdcgAICeEHmr+07krTJrt3VjY13ea54T6c88+FuO+LnG9GQCgV1X8POI lhISAEjoPpzErokSmTog+0tBPZdNbW+sM9v6BcJX91cPA3kYUmbGFk3fOJb2wRrSKGyq Z/LBK9gmn2GJHBV8S2MecPheW56GHJV6I2nN0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=FWVYjFfIIe+qY04H734qWucJ1T7JU5SJXMfcm3nyZe8=; b=rM4ivdgdZFK3mgfIdx8yVb2QcioulEq96jYg8amEdhXZbD1lljiWt2pC9B3Vzi8Auz MmKkEICqMEpOfdFwwudXE1esJ6/pfz1d+Lg92heTgutkVrUZYICxZ/16msx5cVzt8Lgb HeKI99Sm+zfDj3O3/bS/QHTPElm+bGcauCqeABMyEm0moUOgyOMm6KFw1fJUjRIaaOd6 4OcO+6C0iMpPnS7f1RwMtNH7QZNZjYxnnus5LAfoU8q8myNCpItY5gZdi4ImNQtAN4qb F9298eFUs8R+QYayWHz7/um+Rnl5dyCP1LxooN/r/XcJxALQNOEJa4fVQ+fPrTrykMnA Cs9g== X-Gm-Message-State: APjAAAW/q87xdfgjWen+ikBIoePelzcXPj+rCcmp7ZJBlgmbe7oLWGVJ eNpXJuN2jU/qLDaZwevm0FwduA== X-Google-Smtp-Source: APXvYqylwQx/pxF9jNXq8V9+2c/EaY/yAeM5ESWygh8UA426HKAmV3tZgouZQbhsGnnQMhE/2md2DQ== X-Received: by 2002:a9d:650f:: with SMTP id i15mr58642823otl.97.1577734221397; Mon, 30 Dec 2019 11:30:21 -0800 (PST) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id j186sm8998876oih.55.2019.12.30.11.30.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Dec 2019 11:30:20 -0800 (PST) Date: Mon, 30 Dec 2019 11:30:19 -0800 From: Kees Cook To: =?iso-8859-1?Q?Micka=EBl_Sala=FCn?= Cc: KP Singh , linux-kernel@vger.kernel.org, bpf@vger.kernel.org, linux-security-module@vger.kernel.org, Alexei Starovoitov , Daniel Borkmann , James Morris , Thomas Garnier , Michael Halcrow , Paul Turner , Brendan Gregg , Jann Horn , Matthew Garrett , Christian Brauner , Florent Revest , Brendan Jackman , Martin KaFai Lau , Song Liu , Yonghong Song , "Serge E. Hallyn" , Mauro Carvalho Chehab , "David S. Miller" , Greg Kroah-Hartman , Nicolas Ferre , Stanislav Fomichev , Quentin Monnet , Andrey Ignatov , Joe Stringer , =?iso-8859-1?Q?Micka=EBl_Sala=FCn?= Subject: Re: [PATCH bpf-next v1 00/13] MAC and Audit policy using eBPF (KRSI) Message-ID: <201912301128.B37D55AB44@keescook> References: <20191220154208.15895-1-kpsingh@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On Fri, Dec 20, 2019 at 11:46:47PM +0100, Mickaël Salaün wrote: > I'm working on a version of Landlock without eBPF, but still with the > initial sought properties: safe unprivileged composability, modularity, and > dynamic update. I'll send this version soon. > > I hope that the work and experience from Landlock to bring eBPF to LSM will > continue to be used through KRSI. Landlock will now focus on the > unprivileged sandboxing part, without eBPF. Stay tuned! Will it end up looking at all like pledge? I'm still struggling to come up with a sensible pledge-like design on top of seccomp, especially given the need to have it very closely tied to the running libc... -- Kees Cook