From owner-freebsd-questions@freebsd.org Tue Jan 10 00:48:45 2017 Return-Path: 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 E098DCA67F5 for ; Tue, 10 Jan 2017 00:48:45 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 B169E141E for ; Tue, 10 Jan 2017 00:48:45 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-pf0-x244.google.com with SMTP id b22so9566049pfd.3 for ; Mon, 09 Jan 2017 16:48:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=fDoaOvUO35/s4kFofeMW9fEeu3ckJxo6bP3vJrZDF2k=; b=JWdquvDocbF6PW+zeLwRc7l8twYpzScJR/4X28fqcdUCcK7OWq4Y2kouDNy6R94QJB bXo480TrxjZ6nCHUhbrC0kc9H+IEnwWZDmSVmziANPOIs228mjFn0MohN90PqaNG44hI XCYcU8zuG8r5f1SMpP498KMjOxoWvN84POECPTyCkBAfdVPsqUF4HzsPeMAY9xLwnfbW jK4ulVWGfgWYmHG+O80fXtEpoUvyn1ieO6/4uKudsFFo01tjEvYOLdkZ0WedKwcT2fO9 xyA9ld6NPG63AdRn2wLW49g4knWEy956oaoBv1ytLo4MpZGTTm3wqiPlYpmsfja4tCRF ND6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=fDoaOvUO35/s4kFofeMW9fEeu3ckJxo6bP3vJrZDF2k=; b=HWLYmGejlC7eL6ilIFIhuCwqhxCxUaoXMn+DfzcWKk7Mlr5jjzZ7/6NUAiR+Xre7jv pMoYMAIf7AtaDXWyOF9AsWxp4DZSRq++A32Ky2lvh+tIguY/uJq87D6guV6KM+JS7RDn 5L+yxKC8jytwqlPGuGk4cOnaNzikN/Te1w+MfcmXbhr+yGH1J2Um8hItIjzkF5PR2Beh Rl38s2UiuiyIejMmGmWWbqACZGnfUPNjtfAI2nLaHIPc5At059NKBZzuHjt2hrT0z33I 0fvAp9Ix/naab1r3jKi3qT3bX0rD+RdhDg5Hbdm+p86UUIwgUjR1EbbAvOzuqSOOzJ4P kdbg== X-Gm-Message-State: AIkVDXIMvRymiOlfPndmN92DwRuQTlHUJxt4wJBwO1vs60B+uflIqqTOjkmfAfxPplshbA== X-Received: by 10.99.189.26 with SMTP id a26mr629481pgf.67.1484009325348; Mon, 09 Jan 2017 16:48:45 -0800 (PST) Received: from [192.168.1.103] ([120.29.76.161]) by smtp.googlemail.com with ESMTPSA id d1sm212791pfb.76.2017.01.09.16.48.43 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 09 Jan 2017 16:48:44 -0800 (PST) Message-ID: <58742F6C.8050801@gmail.com> Date: Tue, 10 Jan 2017 08:48:44 +0800 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Pavel Timofeev CC: freebsd-questions@freebsd.org Subject: Re: How to allow mlock(2) in jail? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 00:48:46 -0000 Pavel Timofeev wrote: > Hello! > 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? > > P. S. I know, I can disable mlock(2) use in vault config as workaround. > A jail has no kernel so no memory to lock.