From owner-freebsd-jail@freebsd.org  Tue Jun 26 19:53:17 2018
Return-Path: <owner-freebsd-jail@freebsd.org>
Delivered-To: freebsd-jail@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 D600A1015AB4;
 Tue, 26 Jun 2018 19:53:17 +0000 (UTC)
 (envelope-from marquis@roble.com)
Received: from mx5.roble.com (mx5.roble.com [209.237.23.5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7A30D818AA;
 Tue, 26 Jun 2018 19:53:17 +0000 (UTC)
 (envelope-from marquis@roble.com)
Received: from roble.com (roble.com [209.237.23.50])
 by mx5.roble.com (Postfix) with ESMTP id BFE7521881;
 Tue, 26 Jun 2018 12:53:08 -0700 (PDT)
Date: Tue, 26 Jun 2018 12:53:08 -0700 (PDT)
From: Roger Marquis <marquis@roble.com>
To: freebsd-security@freebsd.org, freebsd-jail@freebsd.org
Subject: Jailing {open,}ntpd
Message-ID: <nycvar.OFS.7.76.444.1806261238560.57821@mx.roble.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-BeenThere: freebsd-jail@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Discussion about FreeBSD jail\(8\)" <freebsd-jail.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-jail/>
List-Post: <mailto:freebsd-jail@freebsd.org>
List-Help: <mailto:freebsd-jail-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 19:53:18 -0000

Has anyone configured {open,}ntpd to run in a FreeBSD jail or Linux
container?  Can it be done in such a way that a breached daemon would
not have access to the host?

Roger Marquis