Re: RFC(v2): Audit Kernel Container IDs

Steve Grubb
2017-10-18T00:23:01Z

On Tuesday, October 17, 2017 1:57:43 PM EDT James Bottomley wrote:
> > > > The idea is that processes spawned into a container would be
> > > > labelled by the container orchestration system. It's unclear
> > > > what should happen to processes using nsenter after the fact, but
> > > > policy for that should be up to the orchestration system.
> > >
> > > I'm fine with that. The user space policy can be anything y'all
> > > like.
> >
> > I think there should be a login event.
>
> I thought you wanted this for containers? Container creation doesn't
> have login events. In an unprivileged orchestration system it may be
> hard to synthetically manufacture them.

I realize this. This work is very similar to problems we've solved 12 years
ago. We'll figure out what the right name is for it down the road. But the
concept is the same. If something enters a container, we need to know about
it. It needs to get tagged and be associated with the container. The way this
was solved for the loginuid problem was to add a session identifier so that
new logins of the same loginuid can coexist and we can trace actions back to a
specific login. I'd think we can apply lessons learned from a while back to
make container identification act similarly.

-Steve