From owner-freebsd-security@freebsd.org Sat Mar 17 19:01:55 2018 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB350F60E1B for ; Sat, 17 Mar 2018 19:01:55 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4186669E28 for ; Sat, 17 Mar 2018 19:01:55 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-lf0-f45.google.com with SMTP id h127-v6so19897199lfg.12 for ; Sat, 17 Mar 2018 12:01:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=GKWC0L0rLpt7+9tKZh7XWbPBd05BbQDFjotUTXA45pc=; b=IIXOBgb5WFzoKrK6gDAzP+t5keoZzugL0hD/N21zZYZ2DIr4iyGwG/3dsOpf8Ycin7 oqqrTEGnVqWRON3+5dkrHDwNzn2gvAX2Y0qjcbj9BZm+sISHU82zLAvYYhMVMZDIRhB0 vGwTorHAaKGtz3Tu+0LxowdRaO5H82rahs6FSX653U0SBkfgSdDH9gqerbLF+/XZpS1F AiY0w+L3AE3ynE2UWxpISsyuL31bv6A6ho3JwMpwxnb21q+vX2XR+KdyMeGRRc0pb6Al TOYVf8v4joNLWtaVrM44I/to4RYhnGirl1ipoVzGssCfT0q+DApL59cVaaoSo5aVu3Td YloA== X-Gm-Message-State: AElRT7EhHuH/c0bSz9MXC+1tZkMT5+tD1ur+TXZettxzKFYnJiVsH2BW QvRD6JIms7TgUmO4lTcAbVpuK3hI X-Google-Smtp-Source: AG47ELs1mz1+kT1au++6QJQP9rJysDSxuBeWWAnyW5Ixo4ikoVIgcSDU7CPmBGfSdcH947cw8Eg2cQ== X-Received: by 2002:a19:280e:: with SMTP id o14-v6mr4404789lfo.121.1521313308619; Sat, 17 Mar 2018 12:01:48 -0700 (PDT) Received: from oxy (89-76-8-18.dynamic.chello.pl. [89.76.8.18]) by smtp.gmail.com with ESMTPSA id o192-v6sm2438707lfo.17.2018.03.17.12.01.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 17 Mar 2018 12:01:48 -0700 (PDT) Date: Sat, 17 Mar 2018 20:02:27 +0100 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Eitan Adler Cc: Christian Peron , "freebsd-security@freebsd.org" Subject: Re: auditing users within a jail Message-ID: <20180317200227.0be58cc3@oxy> In-Reply-To: References: <20180312031746.GB7114@cps-macbook-pro.lan> <20180314141301.7bdd2d3d@oxy> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2018 19:01:55 -0000 On Sat, 17 Mar 2018 04:48:52 -0700 Eitan Adler wrote: >On 14 March 2018 at 06:13, Mateusz Piotrowski <0mp@freebsd.org> wrote: >> On Sun, 11 Mar 2018 22:17:47 -0500 >> Christian Peron wrote: >> >>>However, it is possible for processes in jails to produce audit >>>records. The processes just need an audit mask. Since audit masks >>>(configurations) are inherited across forks, you could set a global >>>audit configuration for the jail using the following tool (or >>>something like it): >>> >>>https://github.com/csjayp/setaudit (I just dropped it on to github) >> >> FYI, I'll submit a new setaudit port if Christian decides to pull in >> my enhancements. > >We chatted a bit offline, but thanks for the info! That was really >helpful. :) BTW, the new port is already waiting on Bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226627