All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michele Giacomoli <michele.giacomoli@mynet.it>
To: linux-audit@redhat.com
Subject: Re: Audit, lxc containers and logged paths
Date: Thu, 30 Jun 2016 19:40:09 +0200	[thread overview]
Message-ID: <57755979.6060609@mynet.it> (raw)
In-Reply-To: <57755679.7090007@mynet.it>

Sorry, forgot to mention:
Host is Ubuntu 14.04, while guests are different Ubuntu versions
Audit is installed from Ubuntu repos (version 1:2.3.2-2ubuntu1)

Thank you

Il 30/06/2016 19:27, Michele Giacomoli ha scritto:
> Hello everybody,
>
> I need to watch folders inside unprivileged linux containers. From 
> what I know it's not possible to run audit inside a lxc guest, so I 
> set up audit inside the host to log access to dirs using absolute path 
> (e.g. /var/lib/lxc/mycontainer/rootfs/etc/) and it works, but giving a 
> look at the logs I found that both the paths of the executable and the 
> path that has been accessed are relative to the container (i.e. 
> /bin/ls and /etc/passwd), so I don't have a clue of which is the 
> container that generated the record. I could compare the uid that 
> generated it whith the uids set for the containers, but it seems an 
> ugly solution.
>
> Can audit be configured for logging the absolute paths, or give me a 
> hint of the container that generated the record?
>
> Best regards
> Michele

  reply	other threads:[~2016-06-30 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 17:27 Audit, lxc containers and logged paths Michele Giacomoli
2016-06-30 17:40 ` Michele Giacomoli [this message]
2016-06-30 18:09 ` Richard Guy Briggs
2016-07-01  7:40   ` Michele Giacomoli

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=57755979.6060609@mynet.it \
    --to=michele.giacomoli@mynet.it \
    --cc=linux-audit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.