From owner-freebsd-questions@freebsd.org  Tue Jan 10 01:04:56 2017
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DB25CA6CA2
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Tue, 10 Jan 2017 01:04:56 +0000 (UTC)
 (envelope-from citrin+bsd@citrin.ru)
Received: from hz.citrin.ru (hz.citrin.ru [IPv6:2a01:4f8:d16:10c3::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E28CF1C71
 for <freebsd-questions@freebsd.org>; Tue, 10 Jan 2017 01:04:55 +0000 (UTC)
 (envelope-from citrin+bsd@citrin.ru)
Received: from x220.lan (c-24-60-168-172.hsd1.ct.comcast.net [24.60.168.172])
 by hz.citrin.ru (Postfix) with ESMTPSA id 1165429A32E
 for <freebsd-questions@freebsd.org>; Tue, 10 Jan 2017 01:04:52 +0000 (UTC)
Subject: Re: How to allow mlock(2) in jail?
To: freebsd-questions@freebsd.org
References: <CAAoTqftm_mMDp27CVXns3FFJwJXAWUeiX0hqq-DQUgZC+=aGRQ@mail.gmail.com>
From: Anton Yuzhaninov <citrin+bsd@citrin.ru>
Message-ID: <ba024cae-82c1-8260-06e0-cd222f0c1577@citrin.ru>
Date: Mon, 9 Jan 2017 20:04:51 -0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <CAAoTqftm_mMDp27CVXns3FFJwJXAWUeiX0hqq-DQUgZC+=aGRQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrin.ru; s=s0;
 t=1484010293; bh=UMjAvUBiIWQxbqvP54Q1GLTTQ09blSU8/BmiSBCIDdc=;
 h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding;
 b=Ch/7mq+ayLI0Cm6lP6q44ppUk9Oj4EwQou4YSCDWJBOHbi51jURbnLd3rjMkQctXQej3UkS4DivkuJYI9bBvMHVCN3XEo1KXRFTUXwlwpbJ/uAnhZrwoKyqshWC4oWFSWdKel+aysSIaTyxP4YZOVkDJ5nII19v1NbgjlvGxl7w=
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2017 01:04:56 -0000

On 01/09/17 09:31, Pavel Timofeev wrote:
> I'm trying to deploy security/vault in freebsd jail.
> Usually this tool locks some memory for security reason.
>
> I can run vault on my bare system without any problems. But in jail it
> complains mlock(2) is not available.
> So my question is how to allow mlock(2) in jail?

Currently mlock(2) is not available inside jail.

I think it is possible to implement new jail parameter to allow mlock.