[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52A52599.3070502@cn.fujitsu.com>
Date: Mon, 09 Dec 2013 10:06:17 +0800
From: Gao feng <gaofeng@...fujitsu.com>
To: "Serge E. Hallyn" <serge@...lyn.com>
CC: linux-kernel@...r.kernel.org, linux-audit@...hat.com,
Richard Guy Briggs <rgb@...hat.com>,
containers@...ts.linux-foundation.org, serge.hallyn@...ntu.com,
eparis@...hat.com, ebiederm@...ssion.com, sgrubb@...hat.com
Subject: Re: [RFC Part1 PATCH 00/20 v2] Add namespace support for audit
On 12/07/2013 06:12 AM, Serge E. Hallyn wrote:
> Quoting Gao feng (gaofeng@...fujitsu.com):
>> Hi
>>
>> On 10/24/2013 03:31 PM, Gao feng wrote:
>>> Here is the v1 patchset: http://lwn.net/Articles/549546/
>>>
>>> The main target of this patchset is allowing user in audit
>>> namespace to generate the USER_MSG type of audit message,
>>> some userspace tools need to generate audit message, or
>>> these tools will broken.
>>>
>>
>> I really need this feature, right now,some process such as
>> logind are broken in container becase we leak of this feature.
>
> Your set doesn't address loginuid though right? How exactly do you
> expect to do that? If user violates MAC policy and audit msg is
> sent to init user ns by mac subsys, you need the loginuid from
> init_audit_ns. where will that be stored if you allow updates
> of loginuid in auditns?
>
This patchset doesn't include the loginuid part.
the loginuid is stored in task as before.
In my opinion, when task creates a new audit namespace, this task's
loginuid will be reset to zero, so the children tasks can set their
loginuid. Does this change break the MAC?
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists