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=-2.4 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,USER_AGENT_SANE_1 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 D497BC2D0DB for ; Wed, 22 Jan 2020 10:03:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 960CF2465A for ; Wed, 22 Jan 2020 10:03:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ieee.org header.i=@ieee.org header.b="AOP49hkl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729263AbgAVKDJ (ORCPT ); Wed, 22 Jan 2020 05:03:09 -0500 Received: from mail-qv1-f50.google.com ([209.85.219.50]:42101 "EHLO mail-qv1-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729074AbgAVKDJ (ORCPT ); Wed, 22 Jan 2020 05:03:09 -0500 Received: by mail-qv1-f50.google.com with SMTP id dc14so2921548qvb.9 for ; Wed, 22 Jan 2020 02:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=5/3OELspn/o3+Yeja+ukzugWp9hO1+8exZU20307W64=; b=AOP49hklPdDZWGNrWXFPek4otrUsRrK8w6FbtV/hUk/lBT6ti4GEKpN0Q53WtUI7N5 AqjhdjHYaBRVJH2oxC0RjlD6OxwDUJzuNMCf4tk/Huf9ZGiwCzi0DnzxqwwKK/aMEtEK Upmz3uruJQg4TvAbQtVhuqKLuvpuBDJF1NMpM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5/3OELspn/o3+Yeja+ukzugWp9hO1+8exZU20307W64=; b=MZvgiPY4eoCuosaOkkq563zQBSBNHXWZdac7bsjNDIIZDkK2vnt3Ldd///ZOPU12ZE 0NLGZPcVp2JfJmUFdK4g5bajipi8tuEvwr1UBMRjBwS6oBlzKtyy0MLmryJiwkti+8Ej et3Tgzb3Mubcju/YyoFww4QtWeRmAz51ysW+As/fZKd8pznR5cLCbMt6By5WYZvEDpl7 z85P2G9QhqwNoVeQLgU9QLLOM6rPZFDkOybio7UKgYFzFaZtLWXRRPVIuCGE2OsmYhPd 0lsl5Yvp0iHwmEvLsNCRuaaeVVSJEoSvSeKCFvKKuGGLfYFWBnFQIRB7DTbKWHOsWTdq V1fQ== X-Gm-Message-State: APjAAAXkPhXjcStocpjy0FPHdzC8/XiHuziksxgzYk3XbbSrEJFD8lJs 2x3fgF4gpX0eTOBNfda/uflyN0rsr7wo+A== X-Google-Smtp-Source: APXvYqzuREdnUUhuBX7uTVptjnA2I5yuJeJJFHepLOeYWaPHC+aSlRGVDm4AtfOWDe4yAkBXNd8jdA== X-Received: by 2002:a0c:8bd2:: with SMTP id a18mr9417753qvc.38.1579687387886; Wed, 22 Jan 2020 02:03:07 -0800 (PST) Received: from fedora.pebenito.net (pool-108-15-23-247.bltmmd.fios.verizon.net. [108.15.23.247]) by smtp.gmail.com with ESMTPSA id m3sm273885qkk.90.2020.01.22.02.03.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Jan 2020 02:03:07 -0800 (PST) Subject: Re: [RFC] files: Make files_{relabel,manage}_non_security_types work on all file types To: Henrik Grindal Bakken Cc: selinux-refpolicy@vger.kernel.org References: <20200117231500.59904-1-hgb@ifi.uio.no> <875zh4aop3.fsf@cisco.com> From: Chris PeBenito Message-ID: <068afebc-bee1-0d1e-ed37-e1473f66f982@ieee.org> Date: Wed, 22 Jan 2020 05:03:06 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <875zh4aop3.fsf@cisco.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: selinux-refpolicy-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org On 1/21/20 9:06 AM, Henrik Grindal Bakken wrote: > Chris PeBenito writes: > >> On 1/17/20 6:15 PM, Henrik Grindal Bakken wrote: >>> From: Henrik Grindal Bakken >>> >>> This is the same behavious as files_*_non_auth_types have. > > [...] > >> NAK. Access per object class is already split up across separate >> interfaces, so doing this would be confusing and prevent someone from >> getting file-only access. > > Ok. Then I would recomment rewriting the systemd_tmpfiles_t rules a > bit, because today it has a serious amount of AVC violations for pretty > standard usage. Perhaps. However, it depends on what you consider standard usage. > There are no matching interfaces for lnk_files, at least. Any > suggestions as to how to set up the tmpfiles rules? By adding new interfaces that are like the existing files_manage_non_security_files() interface, but for lnk_file. -- Chris PeBenito