From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 17:19:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4E6E16A4CE for ; Sat, 15 Nov 2003 17:19:11 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8958F43FCB for ; Sat, 15 Nov 2003 17:19:10 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id BDBB133C8E; Sat, 15 Nov 2003 21:17:14 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id BB08833C64 for ; Sat, 15 Nov 2003 21:17:14 -0400 (AST) Date: Sat, 15 Nov 2003 21:17:14 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20031115211530.J34088@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: memory locking in a jail? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 01:19:11 -0000 With gpg setuid root, I'm getting the following 'insecure memory' issue when running inside of a jail: gpg: WARNING: using insecure memory! from the FAQ, it has to do with memory locking ... is this something that can't be done inside of a jail? Or just an issue with jail in 4.x?