Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2133322rwd; Thu, 15 Jun 2023 22:52:16 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4wF13g4tLt8yVZARxMQZBMCWhsYVJM/QHVWO60sgh7AC2PQ4n75qscytwXl2vuvSdOtbZ6 X-Received: by 2002:a05:6358:c601:b0:12b:c47f:5df4 with SMTP id fd1-20020a056358c60100b0012bc47f5df4mr744273rwb.23.1686894736399; Thu, 15 Jun 2023 22:52:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686894736; cv=none; d=google.com; s=arc-20160816; b=F1jNQMiot5F1GGDxrmvGUhZOhSH5QPDNPO5EVLT1egRQLqoi7PyAK/3xqw828SGqm6 GIDsG9xAMjE+4+Ev+VfwCiEiqBfkx1M+BKW8bVgyynBFscG+w4yAtx48/LoCEitfI4ng yIQEC65er/RRjGPuMncy+jZx6sTvQuTGn0lSfa2S6y+5K/tJL1sMI9B4oPfZ4C0Qh9lY dMoIBUc7VaHSXWWcHfzN8JphnckJnpJK2wR9hB5rIaZrx0yfjSOUJF5w1jK9lcs4ROpO fYkV6S0Gl7ee1rl9DbSKL6dV/tog46PPYa/Bycb2UmJZGmekAgUo9kctuS6Cd0ceSnvM LMmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=bW+e6H/DTEN8UNhvPywJwaMdGD4jgcUzw/Lz558z0qc=; b=C4HqLv/LyOsCOmNkBfXmwS6T0B+QRs2KZf6YFO2BAY+vskR/3on3rijymVq0As6yFu vSdXeFI0VUqCNH4U8zThbdJEp50QNknZLOjpIL7dnNSmtwmLc/uk0g1/ifTSQ2A3QKcq aGut1/g6r27+xWHSM/r0YJuVEPLjVrg8Yant8ldcj+vZqrL7QitQkZcgR8DNrDtI2Aj5 aUEKaeStuBbH5EfA/pmCGcOe5/f0YxybMDz58dPXpBLFsV+T2WM822ktracqYVFs3Ds7 s80v3E/f7w7TvzMamxnj1GCNUHgfDDQq4nCkPGfFzorBcywBGHPrXKZrrwolBuliM1G4 6toQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="N/DNsoRd"; spf=pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=selinux-refpolicy-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p9-20020a639509000000b0052868a865d4si14128949pgd.553.2023.06.15.22.52.11; Thu, 15 Jun 2023 22:52:16 -0700 (PDT) Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="N/DNsoRd"; spf=pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=selinux-refpolicy-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231807AbjFPFoT (ORCPT + 21 others); Fri, 16 Jun 2023 01:44:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38760 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229657AbjFPFoT (ORCPT ); Fri, 16 Jun 2023 01:44:19 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2306A1715 for ; Thu, 15 Jun 2023 22:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1686894210; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=bW+e6H/DTEN8UNhvPywJwaMdGD4jgcUzw/Lz558z0qc=; b=N/DNsoRdH16bjwbv15XILknpyG3k4Xy3aQcQg0k5aDl8/RnbXUH0VL6LFm/wd2wOmSyC+Z MRHY2QR87B1aD7IFPx5yQsTeAS0bn4ouAH0Obc0ufocyZI/YqCaWUqvzD8mRfXQvkDOjFD LpGYL3A81Sq4lxfWAsJ+ziJ8wrN2az0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-619-Bn5NCHZoN-mknGzBhRFLZA-1; Fri, 16 Jun 2023 01:43:28 -0400 X-MC-Unique: Bn5NCHZoN-mknGzBhRFLZA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5C69E85A5BB; Fri, 16 Jun 2023 05:43:28 +0000 (UTC) Received: from localhost (unknown [10.45.224.112]) by smtp.corp.redhat.com (Postfix) with ESMTP id F35121415102; Fri, 16 Jun 2023 05:43:27 +0000 (UTC) From: Petr Lautrbach To: Paul Moore , Christian =?utf-8?Q?G=C3=B6ttsche?= , selinux@vger.kernel.org, selinux-refpolicy@vger.kernel.org Cc: Lennart Poettering Subject: Re: SELinux and systemd integration In-Reply-To: References: Date: Fri, 16 Jun 2023 07:43:27 +0200 Message-ID: <87r0qcotc0.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org Paul Moore writes: > Hello all, > > Amongst Christian's various other SELinux contributions, over the past > several years Christian has been working on improving the SELinux > integration in systemd. One of the things that Christian has been > working on is revamping the SELinux permissions that systemd uses for > unitfile operations, both to resolve problems and generally improve > the mapping of permissions to systemd operations. As this work has > been languishing for several years, I would like to see if we can get > things "unstuck" by proposing two things: > > 1. I've provided links to the systemd GH PRs below, but I think it > might be helpful if Christian could provide a quick summary of the new > permissions, how they map to systemd operations, and how they map to > the existing SELinux/systemd permissions with a focus on helping > policy developers migrate existing SELinux policies. > > 2. Given the significance of systemd to modern Linux distributions, I > think it might be a good idea if we selected a SELinux "liaison" for > the systemd project. This person, or group of people, would work with > the systemd folks to keep the SELinux integration in good working > order, review systemd code as necessary, and help represent the > SELinux project within systemd. > > How does that sound to everyone? If we are in agreement on #2, and > assuming he would be willing to help out, I would like to nominate > Christian as our SELinux liaison to systemd; any objections? Anyone > else interested in helping out? I agree with the Christian's nomination. As for #1, I looked on both, but I have to admit that I had a lack of understanding of the problem and so I would need some time to get into it. Therefore I postponed it due to other priorities, (but never come back). If it's still open I'll focus on it next week. > For reference, Christian's systemd PRs on GH: > * https://github.com/systemd/systemd/pull/10023 > * https://github.com/systemd/systemd/pull/20387 > Thanks, Petr