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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED 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 040F9C282D7 for ; Sat, 2 Feb 2019 08:33:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B07EE20844 for ; Sat, 2 Feb 2019 08:33:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=coker.com.au header.i=@coker.com.au header.b="JLJsHk6O" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726659AbfBBIdy (ORCPT ); Sat, 2 Feb 2019 03:33:54 -0500 Received: from smtp.sws.net.au ([46.4.88.250]:32954 "EHLO smtp.sws.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726653AbfBBIdy (ORCPT ); Sat, 2 Feb 2019 03:33:54 -0500 Received: from liv.localnet (localhost [127.0.0.1]) by smtp.sws.net.au (Postfix) with ESMTP id 08F82EFDB for ; Sat, 2 Feb 2019 19:33:50 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coker.com.au; s=2008; t=1549096432; bh=4stT1RJCbf3JDmR/jHXXI733rVGYnkoNreEaijQR37A=; l=309; h=From:To:Subject:Date:From; b=JLJsHk6OqahI4R6yyg1si3XchIob4dFUAIcx9eoPQtyySpE8SCkhJJ5OjcjMoOAix +Ih0zZI9EEV+Fkcg7py/7gueLt7WpEovujs24DXEDtKlkDtJ3zJmqvntxTJNpZLj8N 2YPqTz/gnln8U/w7spf2A3YxajeudaLVb7zNgiNk= From: Russell Coker To: "selinux-refpolicy@vger.kernel.org" Subject: netlink perms Date: Sat, 02 Feb 2019 19:33:44 +1100 Message-ID: <1982409.BaJPGKh2d9@liv> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: selinux-refpolicy-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org define(`create_socket_perms', `{ create rw_socket_perms }') define(`r_netlink_socket_perms', `{ create_socket_perms nlmsg_read }') So r_netlink_socket_perms has write access to the socket. Does this make sense? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/