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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 186E1ECAAD3 for ; Wed, 14 Sep 2022 13:56:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229522AbiINN44 (ORCPT ); Wed, 14 Sep 2022 09:56:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229491AbiINN4z (ORCPT ); Wed, 14 Sep 2022 09:56:55 -0400 Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 39C167755B for ; Wed, 14 Sep 2022 06:56:53 -0700 (PDT) Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-12803ac8113so41126654fac.8 for ; Wed, 14 Sep 2022 06:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Sr2wU3YSWBwhCxEQJoE1i3zQYmbJdpbozpXHeTGBoW0=; b=ddJ2bP5ONY5DKuQ1S5CMRCKFiBt64fU/gIJFOw6Wzw0HNICQv6c5D5pFzA1aUcYRED KhZ1aa/4m355bP/udx5mgE7Y/5n7DjLAJilhZCe2qQINl7vLYXCpfmoCbE9DSDdKmzej pGi9DM9DoX4JB0KtGPjExowSaMea7n0JcmpjBqHjICYAcfCgHBgZ9zMAVvH45o8A0h47 LAjpmOfYngakzp57MDIez+DePZVWTISqbLcAEjBBogJ8AalAIUyfbgerHDiSxQdWEkqI yzcD5573bbkaHt7a3ERKPrk0leJ0LmOmLY+HBKRhQTctzvQ1YhHrJijLv3Xj/ERdmDAF hB5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Sr2wU3YSWBwhCxEQJoE1i3zQYmbJdpbozpXHeTGBoW0=; b=sBgOH8x6amYQ6qg8FcoyopRy3YWgHDPvCcPBsNjrVawcAx5WXP9Bqia37BcmQF/8mY bD+obYDLAR3mhEcnHn1mYoG697aZ4A1qhPj4d/deOMrMSmouyim+HeP2s2WpNEf6rBff yNeOuF717uA9E8AOqKibfYJyjRpDsCks67hiMmPyFLsClquaEEv5YQgVsUBrBliSV0Hd R60y0xheSROSuLuERgMJHnNJS+YWCnGKefbtq9neVBoDOa7o8gd73lNIC3yW+F6FDW7l kvEYkWFlyGNCQ5SxeCgxP1BI/3H4G7pZsaVsururIDHLM0J7wgl3Jqoe1C/GKIFowiFf Jk5Q== X-Gm-Message-State: ACgBeo2F0+RdgAz4mIfCUW3xtMzqN2kDbY3iLOpcUf5fljwMxyVTAnnU 6Tm0pOgnT/6+2bSu2vDyxVF3zuXUCNu/Yska5VOG X-Google-Smtp-Source: AA6agR4BaYOtQoQqm2IcpyBcCdUKTptJ3Ojuz61FIJFDzR2uCD7XPdaY1McbizNfu7fWAxQvXZ3gN+N3oInFdZD8jHQ= X-Received: by 2002:a05:6870:178b:b0:12b:c621:b7a9 with SMTP id r11-20020a056870178b00b0012bc621b7a9mr2476963oae.41.1663163812506; Wed, 14 Sep 2022 06:56:52 -0700 (PDT) MIME-Version: 1.0 References: <791e13b5-bebd-12fc-53de-e9a86df23836.ref@schaufler-ca.com> <791e13b5-bebd-12fc-53de-e9a86df23836@schaufler-ca.com> <8ac2731c-a1db-df7b-3690-dac2b371e431@I-love.SAKURA.ne.jp> <854c05ad-888e-b882-bb97-65f4ca289bc6@I-love.SAKURA.ne.jp> In-Reply-To: <854c05ad-888e-b882-bb97-65f4ca289bc6@I-love.SAKURA.ne.jp> From: Paul Moore Date: Wed, 14 Sep 2022 09:56:41 -0400 Message-ID: Subject: Re: LSM stacking in next for 6.1? To: Tetsuo Handa Cc: Casey Schaufler , LSM List , James Morris , linux-audit@redhat.com, John Johansen , Mimi Zohar , keescook@chromium.org, SElinux list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: selinux@vger.kernel.org On Fri, Sep 9, 2022 at 7:33 AM Tetsuo Handa wrote: > On 2022/09/09 3:52, Paul Moore wrote: > > At least one of those, Landlock, has been merged upstream and is now > > available in modern released Linux Kernels. As far as the other LSMs > > are concerned, I don't recall there ever being significant interest > > among other developers or users to warrant their inclusion upstream. > > If the authors believe that has changed, or is simply not true, they > > are always welcome to post their patches again for discussion, review, > > and potential upstreaming. However, I will caution that it is > > becoming increasingly difficult for people to find time to review > > potential new LSMs so it may a while to attract sufficient comments > > and feedback. > > Inclusion into upstream is far from the goal. For better or worse, there is a long history of the upstream Linux Kernel focusing only on in-tree kernel code, I see no reason why we should change that now for LSMs. I am sorry that this approach negatively affects the LSMs you mentioned, but if they are not interested in being merged upstream there is not much we can do to help. -- paul-moore.com 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 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E7827C6FA82 for ; Wed, 14 Sep 2022 13:57:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1663163820; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=SoDaQVVdYIaPTErsGjQp8IIXzEULiuGfIfbiSANL3Kk=; b=Xm/JKh91pgiqhw7V3sevwt//mC+tVfqrVQ27DTSNNZ66QNS3JfEsSjrEiq8H0FSSEKTeFV U9aXMiF329PQZkCvH2AFp+lEfrN/i3OLvoT6o1NtNMHvAlwAIpDnWy0dJacCSriOtmrWmU BB5ROF9HJxhDoWikhYkaEX10fNj+XFc= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-446-K1_QZsxROFmvHgNVr_11nA-1; Wed, 14 Sep 2022 09:56:57 -0400 X-MC-Unique: K1_QZsxROFmvHgNVr_11nA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3F9333C025C0; Wed, 14 Sep 2022 13:56:56 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 13238C15BA4; Wed, 14 Sep 2022 13:56:56 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id D9DDA1946A4E; Wed, 14 Sep 2022 13:56:55 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 1852F1946A4A for ; Wed, 14 Sep 2022 13:56:55 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id EF6682027062; Wed, 14 Sep 2022 13:56:54 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast05.extmail.prod.ext.rdu2.redhat.com [10.11.55.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EBA892027061 for ; Wed, 14 Sep 2022 13:56:54 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D167D882823 for ; Wed, 14 Sep 2022 13:56:54 +0000 (UTC) Received: from mail-oa1-f52.google.com (mail-oa1-f52.google.com [209.85.160.52]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-144-3z7AGr6mMbSKzZb7jymIPg-1; Wed, 14 Sep 2022 09:56:53 -0400 X-MC-Unique: 3z7AGr6mMbSKzZb7jymIPg-1 Received: by mail-oa1-f52.google.com with SMTP id 586e51a60fabf-1279948d93dso41087125fac.10 for ; Wed, 14 Sep 2022 06:56:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Sr2wU3YSWBwhCxEQJoE1i3zQYmbJdpbozpXHeTGBoW0=; b=TPKLqiGqERlctEbQ+ZwFOBUP+w1Twe1Pf3r4ve3VVfHAthVazARKIJ7yBpgNHEzRjD +7kq0bi6TOnk8xpPe+nfKYu4ieLYM/4xGL0D9VbAmBHv7BlS66947tK20EKs8sotIxrB MnO64jGjBgrOaR01Qdu3May7lvTqI8p5zL9YdVJWdHd9DALTn3USBfq7A3ykI1GyBPXm vIFkqvvRi+Ogc23DTQrXTsGnmzZDABWY+SCZJO1kth0W1qWwoLVu2uKS1WMRHO+zRix7 8k8OW0rkbrZiS7PtHHHyj2gzpKOuoQbIy6BgrGy7oK8B8cLF12JPeQjovqnlVJEgsGKs 3RkA== X-Gm-Message-State: ACgBeo1ESDlJbpJiranSZzFTDZWr6Rwr1JHcK9/5MpkRF6GGbtRigb0a cP8G6Z2J3DHRwVH2JT3BEwQS5StGv413CzO59T8gM+xg23Y3 X-Google-Smtp-Source: AA6agR4BaYOtQoQqm2IcpyBcCdUKTptJ3Ojuz61FIJFDzR2uCD7XPdaY1McbizNfu7fWAxQvXZ3gN+N3oInFdZD8jHQ= X-Received: by 2002:a05:6870:178b:b0:12b:c621:b7a9 with SMTP id r11-20020a056870178b00b0012bc621b7a9mr2476963oae.41.1663163812506; Wed, 14 Sep 2022 06:56:52 -0700 (PDT) MIME-Version: 1.0 References: <791e13b5-bebd-12fc-53de-e9a86df23836.ref@schaufler-ca.com> <791e13b5-bebd-12fc-53de-e9a86df23836@schaufler-ca.com> <8ac2731c-a1db-df7b-3690-dac2b371e431@I-love.SAKURA.ne.jp> <854c05ad-888e-b882-bb97-65f4ca289bc6@I-love.SAKURA.ne.jp> In-Reply-To: <854c05ad-888e-b882-bb97-65f4ca289bc6@I-love.SAKURA.ne.jp> From: Paul Moore Date: Wed, 14 Sep 2022 09:56:41 -0400 Message-ID: Subject: Re: LSM stacking in next for 6.1? To: Tetsuo Handa X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: John Johansen , SElinux list , James Morris , Mimi Zohar , LSM List , linux-audit@redhat.com Errors-To: linux-audit-bounces@redhat.com Sender: "Linux-audit" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Fri, Sep 9, 2022 at 7:33 AM Tetsuo Handa wrote: > On 2022/09/09 3:52, Paul Moore wrote: > > At least one of those, Landlock, has been merged upstream and is now > > available in modern released Linux Kernels. As far as the other LSMs > > are concerned, I don't recall there ever being significant interest > > among other developers or users to warrant their inclusion upstream. > > If the authors believe that has changed, or is simply not true, they > > are always welcome to post their patches again for discussion, review, > > and potential upstreaming. However, I will caution that it is > > becoming increasingly difficult for people to find time to review > > potential new LSMs so it may a while to attract sufficient comments > > and feedback. > > Inclusion into upstream is far from the goal. For better or worse, there is a long history of the upstream Linux Kernel focusing only on in-tree kernel code, I see no reason why we should change that now for LSMs. I am sorry that this approach negatively affects the LSMs you mentioned, but if they are not interested in being merged upstream there is not much we can do to help. -- paul-moore.com -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit