Re: audit watch rules and docker containers

Hi Richard, Thanks for reviewing the email and my apologies for the formatting issue. This response corrects that.

I looked at Steve's response (with the embedded link) and have also followed your presentation on youtube however I am not clear on the proposed change(s) which will allow the mnt space to be shared between the host and the privileged container. Is this use case even being considered?

Thanks, Rakesh ________________________________ From: Richard Guy Briggs <rgb(a)redhat.com&gt; To: Rakesh <raksac(a)yahoo.com&gt; Cc: &quot;linux-audit(a)redhat.com&quot; <linux-audit(a)redhat.com&gt; Sent: Sunday, March 4, 2018 11:14 PM Subject: Re: audit watch rules and docker containers On 2018-03-03 08:52, Rakesh wrote: > Hello Auditd'ers, Hi Rakesh, (I see, with difficulty, that your output is well-formatted in the HTML attachment, but that isn't useful. Please shut off HTML message formatting and ensure that it looks right in plain text. Also, please use "ls -l" so it sorts in a meaningful order for comparison.) > I am running a privileged container with pid, net, uts space shared with the host. The need is to be able to set file watch rules from the container say > -k /etc -p rw -k containter_rule > and then look for read/write access to files/directories in /var/log/audit/*. > What I am finding is there are no watch events being logged > If I set the same audit watch rule from the host (and not being in the privileged container) I am able to get audit events > Using nsenter to switch namespace (nsenter -t 1 auditctl -k /etc -p rw -k containter_rule) does not help either > I suspect the mnt namespace is different which is causing this oddity in behavior > looking at container process namespace - > test@ubuntu-16:~/audit$ sudo ls -latr /proc/26050/ns[sudo] password for test:total 0dr-xr-xr-x 9 root root 0 Mar 2 16:58 ..dr-x--x--x 2 root root 0 Mar 2 17:46 .lrwxrwxrwx 1 root root 0 Mar 2 17:46 uts -> uts:[4026531838]lrwxrwxrwx 1 root root 0 Mar 2 17:46 user -> user:[4026531837]lrwxrwxrwx 1 root root 0 Mar 2 17:46 pid -> pid:[4026531836]lrwxrwxrwx 1 root root 0 Mar 2 17:46 net -> net:[4026531957]lrwxrwxrwx 1 root root 0 Mar 2 17:46 mnt -> mnt:[4026532517]lrwxrwxrwx 1 root root 0 Mar 2 17:46 ipc -> ipc:[4026532518]lrwxrwxrwx 1 root root 0 Mar 2 17:46 cgroup -> cgroup:[4026531835] > looking at init process namespace - > > test@ubuntu-16:~/audit$ sudo ls -latr /proc/1/nstotal 0dr-xr-xr-x 9 root root 0 Mar 2 10:37 ..lrwxrwxrwx 1 root root 0 Mar 2 10:38 mnt -> mnt:[4026531840]dr-x--x--x 2 root root 0 Mar 2 10:38 .lrwxrwxrwx 1 root root 0 Mar 2 16:47 uts -> uts:[4026531838]lrwxrwxrwx 1 root root 0 Mar 2 16:47 user -> user:[4026531837]lrwxrwxrwx 1 root root 0 Mar 2 16:47 pid -> pid:[4026531836]lrwxrwxrwx 1 root root 0 Mar 2 16:47 net -> net:[4026531957]lrwxrwxrwx 1 root root 0 Mar 2 16:47 ipc -> ipc:[4026531839]lrwxrwxrwx 1 root root 0 Mar 2 16:47 cgroup -> cgroup:[4026531835] After decoding your jumbled mess of output due to HTML and ls options choices, the mount namespaces are different, which would completely explain the problem. > Can someone please suggest with some thoughts on how to make this work. The pending container support mentioned by Steve is not yet complete and some more of the coming changes may help with your issue, but start by understanding that you are examining different filesystems with your rules above. > Thanks,Rakesh - RGB