Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759426AbbEEQIa (ORCPT ); Tue, 5 May 2015 12:08:30 -0400 Received: from out01.mta.xmission.com ([166.70.13.231]:56906 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2993283AbbEEPAe (ORCPT ); Tue, 5 May 2015 11:00:34 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Steve Grubb Cc: Richard Guy Briggs , containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, linux-audit@redhat.com, eparis@parisplace.org, pmoore@redhat.com, arozansk@redhat.com, serge@hallyn.com, zohar@linux.vnet.ibm.com, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, netdev@vger.kernel.org References: <11270b0b1afd0a25b108915673e1e1b38dfeeafa.1429252659.git.rgb@redhat.com> <2487286.y6vyJ9A3er@x2> Date: Tue, 05 May 2015 09:56:03 -0500 In-Reply-To: <2487286.y6vyJ9A3er@x2> (Steve Grubb's message of "Tue, 05 May 2015 10:22:32 -0400") Message-ID: <87pp6fhy4c.fsf@x220.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-AID: U2FsdGVkX1+4A5m4HzWTPdeymds+rMBA75ygvCmfmbc= X-SA-Exim-Connect-IP: 67.3.205.90 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 TVD_RCVD_IP Message was received from an IP address * 0.7 XMSubLong Long Subject * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa06 1397; Body=1 Fuz1=1 Fuz2=1] X-Spam-DCC: XMission; sa06 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Steve Grubb X-Spam-Relay-Country: X-Spam-Timing: total 638 ms - load_scoreonly_sql: 0.12 (0.0%), signal_user_changed: 4.8 (0.7%), b_tie_ro: 3.3 (0.5%), parse: 0.67 (0.1%), extract_message_metadata: 2.5 (0.4%), get_uri_detail_list: 0.98 (0.2%), tests_pri_-1000: 3.6 (0.6%), tests_pri_-950: 1.28 (0.2%), tests_pri_-900: 1.09 (0.2%), tests_pri_-400: 18 (2.8%), check_bayes: 17 (2.6%), b_tokenize: 4.9 (0.8%), b_tok_get_all: 6 (0.9%), b_comp_prob: 1.57 (0.2%), b_tok_touch_all: 2.5 (0.4%), b_finish: 0.60 (0.1%), tests_pri_0: 595 (93.2%), tests_pri_500: 3.6 (0.6%), rewrite_mail: 0.00 (0.0%) Subject: Re: [PATCH V6 05/10] audit: log creation and deletion of namespace instances X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Wed, 24 Sep 2014 11:00:52 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1542 Lines: 33 Steve Grubb writes: > The requirements for auditing of containers should be derived from VPP. In it, > it asks for selectable auditing, selective audit, and selective audit review. > What this means is that we need the container and all its children to have one > identifier that is inserted into all the events that are associated with the > container. That is technically impossible. Nested containers exist. That is when container G is nested in container F which is in turn nested in container E which is in turn nested in container D which is in turn nested in container C which is in turn nested in container B which is nested in container A there is no one label you can put on audit messages from container G which is the ``correct'' one. Or are you proposing that something in container G have labels A B C D E F G included on every audit message? That introduces enough complexity in generating and parsing the messages I wouldn't trust those messages as the least bug in generation and parsing would be a security issue. What is the world is VPP? It sounds like something non-public thing. Certainly it has never been a part of the public container discussion and as such it appears to be completely ridiculous to bring up in a public discussion. Eric -- 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/