Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753748AbbHaQWm (ORCPT ); Mon, 31 Aug 2015 12:22:42 -0400 Received: from mail-lb0-f177.google.com ([209.85.217.177]:36499 "EHLO mail-lb0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752107AbbHaQWk (ORCPT ); Mon, 31 Aug 2015 12:22:40 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 31 Aug 2015 18:22:38 +0200 Message-ID: Subject: Re: kdbus_proc_permission (Re: [GIT PULL] kdbus updates for Greg) From: David Herrmann To: Andy Lutomirski Cc: "linux-kernel@vger.kernel.org" , Greg KH Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1300 Lines: 30 Hi On Mon, Aug 31, 2015 at 5:37 PM, Andy Lutomirski wrote: > On Mon, Aug 24, 2015 at 2:52 AM, David Herrmann wrote: >> On Mon, Aug 10, 2015 at 4:42 AM, Andy Lutomirski wrote: >>> I haven't checked the context in which it's used, but in order for >>> kdbus_proc_permission to do what it claims to do, it appears to be >>> missing calls to security_inode_permission and >>> security_file_permission. >> >> Both are expected to be added by lsm patches (both hooks you mentioned >> are empty if no lsm is selected). > > Will that mean that existing MAC policies stop being fully enforced > (in effect) if kdbus is installed? It means kdbus messages carry information about the sender, which LSMs might prevent you to read via /proc. Just like you can send dbus messages to a peer, which LSM-enhanced dbus-daemon might not allow. If you use LSMs, we clearly advise you to wait for kdbus to gain LSM support. We explicitly support legacy dbus1-compat for exactly such reasons. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/