On Mon, 2017-10-16 at 21:42 -0400, Steve Grubb wrote: > On Monday, October 16, 2017 8:33:40 PM EDT Richard Guy Briggs wrote: > > There is such a thing, but the kernel doesn't know about it > > yet. This same situation exists for loginuid and sessionid which > > are userspace concepts that the kernel tracks for the convenience > > of userspace. As for its name, I'm not particularly picky, so if > > you don't like CAP_CONTAINER_* then I'm fine with > > CAP_AUDIT_CONTAINERID. It really needs to be distinct from > > CAP_AUDIT_WRITE and CAP_AUDIT_CONTROL since we don't want to give > > the ability to set a containerID to any process that is able to do > > audit logging (such as vsftpd) and similarly we don't want to give > > the orchestrator the ability to control the setup of the audit > > daemon. > > A long time ago, we were debating what should guard against rouge > processes from setting the loginuid. Casey argued that the ability to > set the loginuid means they have the ability to control the audit > trail. That means that it should be guarded by CAP_AUDIT_CONTROL. I > think the same logic applies today. The difference is that with loginuid you needed to give processes able to audit also the ability to change it. You do not want to tie the ability to change container ids to the ability to audit. You want to be able to do audit stuff (within the container) without allowing it to change the container id. Of course if we made container id a write-once property maybe there is no need for controls at all, but I'm pretty sure there will be situations where write-once may not be usable in practice. > The ability to arbitrarily set a container ID means the process has > the ability to indirectly control the audit trail. The container Id can be used also for authorization purposes (by other processes on the host), not just audit, I think this is why a separate control has been proposed. Simo. -- Simo Sorce Sr. Principal Software Engineer Red Hat, Inc
