public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: "Miloslav Trmač" <mitr@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
	linux-audit@redhat.com, ebiederm@xmission.com
Subject: Re: [PATCH] audit: listen in all network namespaces
Date: Fri, 2 Aug 2013 09:21:24 -0400 (EDT)	[thread overview]
Message-ID: <628325801.10736120.1375449684794.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1375379837.20145.40.camel@dhcp137-13.rdu.redhat.com>

----- Original Message -----
> I still detest the idea of tieing the audit namespace to the user
> namespace.  My NAK still stands on any such patches.
> 
> I'd think that disjoint namespaces (like networking) instead of
> hierarchical namespaces (like user) would be a lot easier to do.  My
> thoughts have always been about completely disjoint audit namespaces and
> I may have missed the nuance of some of your discussion because it
> didn't really dawn on me you seem to have always been discussing
> hierarchical audit namespace.
> 
> I'm wondering if we want/need both?

Would it be possible to avoid adding more dimensions to the namespace matrix?  I appreciate that the flexibility allows a wide range of use cases, however it also makes reasoning about the security properties extremely difficult.

(If only there were a way to put the genie back to the bottle and have the kernel explicitly recognize something like "virt-like container" or "webhosting-like application isolation" as kernel-space concepts and objects...)
   Mirek

  parent reply	other threads:[~2013-08-02 13:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 20:32 [PATCH] audit: listen in all network namespaces Richard Guy Briggs
2013-07-17  3:54 ` Gao feng
2013-07-19 21:15   ` Richard Guy Briggs
2013-07-22  3:20     ` Gao feng
2013-07-30 17:22       ` Richard Guy Briggs
2013-08-01 17:57         ` Eric Paris
2013-08-02  1:48           ` Gao feng
2013-08-02 13:21           ` Miloslav Trmač [this message]
2013-08-02  1:17         ` Gao feng
     [not found] ` <1374006760-7687-1-git-send-email-rgb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-19  3:59   ` Gao feng
     [not found]     ` <52B26F1A.9070308-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-12-19 18:40       ` Eric Paris
     [not found]         ` <1387478422.29366.33.camel-OjZBOOqb7SR7cYLChsl7DafLeoKvNuZc@public.gmane.org>
2013-12-20  1:35           ` Gao feng
2013-12-20  2:46           ` Gao feng
     [not found]             ` <52B3AF8F.5040607-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-12-20  3:11               ` Eric Paris
2013-12-20  3:45                 ` Gao feng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=628325801.10736120.1375449684794.JavaMail.root@redhat.com \
    --to=mitr@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox