From owner-freebsd-security@freebsd.org Sat Mar 17 11:49:24 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 76DDBF6063A for ; Sat, 17 Mar 2018 11:49:24 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 06C8277A52 for ; Sat, 17 Mar 2018 11:49:23 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22d.google.com with SMTP id y23so8675624ywy.4 for ; Sat, 17 Mar 2018 04:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=o0frceJ+0Ial35UUy+iOBzPaQwESeKRv/zZuy3Wj4ug=; b=cgx0D2/r0s6MjlsKy302c3BLsPLB+3lb+FMwtDNWTSQXKyf0f3zX6gMVENYEbm8mHv CxcypMohCcIiqtxb9iyy+SxnDk0X1uHGc28ZcTM5wZypKzlpsrXr8j9p4QFiBztyVzNy 3UPVfu/nItz8MwocefBRjuWYt2lyiDQrKvrK4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=o0frceJ+0Ial35UUy+iOBzPaQwESeKRv/zZuy3Wj4ug=; b=bxwIGxqWRyZNcKcbg63+d3Ko6VWZ6HpRxUO0fDGZGSCuL3DKD7Cc/r6tENNf85fH2J pHeXr1eEpFZ0Gj+UdvGepBRxGrtTbfLveaV5ymeDtCoTfOBjjByeeHWtTQN3OusvPJ5A JKiC/T2paPzrhHNL5GoDjgTciQVMvP9ZV6C535RkKQeJAJDC+9SMTe09RdQOFpsNiy5a iKW6XuP7dXwXHePd6HGr9mDmkEpgxPOyM2dmFMAm84VU9xGEXeHM8qNz+bqM977ZlPNG SVdymwZGBNvfkJr0v+3N/Mkijj8AYIvAI5Phbx7QPNCUURwIaAixTHOJWM1BNGWOnTCl ObDg== X-Gm-Message-State: AElRT7HW+EOXrjNmU+vb3E4qGC+ap7W5mO7JX1MAlUU+BU0DIrBt1iET WyyKzVc+8HTna9ea/VE6Wd03GGRBJTkiDZ1SfNnLCA== X-Google-Smtp-Source: AG47ELt9CBmtRLbGlHQFCDhk2STeg06vuRmvCVYjMcZyzNkKWuc1Ie6Fogt2Pzh0h/56+ZSyEE03czWdAAwlcRHPuRs= X-Received: by 10.129.120.130 with SMTP id t124mr3069071ywc.37.1521287363123; Sat, 17 Mar 2018 04:49:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:23d2:0:0:0:0:0 with HTTP; Sat, 17 Mar 2018 04:48:52 -0700 (PDT) In-Reply-To: <20180314141301.7bdd2d3d@oxy> References: <20180312031746.GB7114@cps-macbook-pro.lan> <20180314141301.7bdd2d3d@oxy> From: Eitan Adler Date: Sat, 17 Mar 2018 04:48:52 -0700 Message-ID: Subject: Re: auditing users within a jail To: Mateusz Piotrowski <0mp@freebsd.org> Cc: Christian Peron , "freebsd-security@freebsd.org" Content-Type: text/plain; charset="UTF-8" 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 11:49:24 -0000 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. -- Eitan Adler