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=-7.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 D4FA9C11D2F for ; Mon, 24 Feb 2020 15:12:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A8F7020828 for ; Mon, 24 Feb 2020 15:12:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ZvgRvqgZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727686AbgBXPMB (ORCPT ); Mon, 24 Feb 2020 10:12:01 -0500 Received: from mail-lf1-f48.google.com ([209.85.167.48]:43596 "EHLO mail-lf1-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727299AbgBXPMB (ORCPT ); Mon, 24 Feb 2020 10:12:01 -0500 Received: by mail-lf1-f48.google.com with SMTP id s23so7030468lfs.10 for ; Mon, 24 Feb 2020 07:11:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=RvnorISGN0y5RjLAtmmPc3b9+GIk7M+OdwfUtlsRMy4=; b=ZvgRvqgZweLPCY4Ri65fyYiawcPRDV2RBafoXBUJN4lSjoaS2+CjGJF1nTN+G9P12k JAGpGIMre4QoMCfr/xazlbEkPHdKmqfiWSTM2mne1KnUeAYr/MQVIBiSIyfVvapWuObj nq0XCv79LWP346ZDzHMTHENn6SllJtM4IPTT7ui8q2/Xmlb6rQfID87gOIql3CvFt1/H V7MfvZs7w3kPSkcFp61t1U45oQCqscaGu+ORQ5h2aRenNz1cjnC23Nel+dnXY3LFVLne ZeFgFAKkOHXEYkiS3RM7iOeIgQSB9EIxhLsqdG16voEpPEmAWo3d0i+a+aGcYfX8iXL0 vAGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=RvnorISGN0y5RjLAtmmPc3b9+GIk7M+OdwfUtlsRMy4=; b=NaVRN03A31JHSbVEDuDbmiwoBqQkHMwLEEMbdzQczaS4krB0DpddSkfl5ynxcV3dID 7leB2ITSoAXyW2EAf2bpJbATJStF6v9ufnegJ4foqlbNgCZqOfUR9m58eudjWTgD7SGo BxHDCIRo5ZeUtdRo6zgNV34DaqjEp2eTyR5sIdOkZpkkVMkH7BMdxoElZBxhh52eI2QW tG76q7TL/M3svtgqHzlP8Jk7YhUPjIHD/1BHgipRgRum8mzEwkoL2M5LU2wcElKhptL+ TUEQXqZAAIj3mgNw01IedjKkcIr5kJqzLYwdEpnQog8lWyrQ1l62dFEDs17riQQOHcb/ wVfQ== X-Gm-Message-State: APjAAAWMHiuRImimdfOSnlRLLAZFnSXn/uyhRTvp/zSWjdLRKbzsXnHm l6O7Lj+TjkeucCxiaGPBeLLLfgB4 X-Google-Smtp-Source: APXvYqzoTnRMwFo4E6PagjHtzONmZD3S/9xnWOQHtXsfz4pGYOxT1LELKCyJrgLSOUbhUIRu5RfH9A== X-Received: by 2002:a19:3f4f:: with SMTP id m76mr9253708lfa.63.1582557118753; Mon, 24 Feb 2020 07:11:58 -0800 (PST) Received: from [192.168.1.38] (88-114-211-119.elisa-laajakaista.fi. [88.114.211.119]) by smtp.gmail.com with ESMTPSA id b17sm224590lff.79.2020.02.24.07.11.57 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Feb 2020 07:11:58 -0800 (PST) To: selinux-refpolicy@vger.kernel.org From: Topi Miettinen Subject: Access to raw memory: remove or make boolean? Message-ID: <11011d01-844e-c526-a85f-92a7fc985d16@gmail.com> Date: Mon, 24 Feb 2020 17:11:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 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 Hi, I made a PR 192 (https://github.com/SELinuxProject/refpolicy/pull/192) for introducing a new boolean to disable access to raw memory devices (/dev/mem, /dev/kmem, /dev/mergemem, dev/oldmem, /dev/port) because on modern systems, direct access shouldn't be needed anymore. Chris PeBenito asked to propose to this list whether instead of boolean, the access should be removed unconditionally if it's no longer needed. I think boolean could be useful for those systems where this is still needed but still use latest reference policy. -Topi Miettinen