From owner-freebsd-security Fri Dec 24 10:25:30 1999 Delivered-To: freebsd-security@freebsd.org Received: from oberon.dnai.com (oberon.dnai.com [207.181.194.97]) by hub.freebsd.org (Postfix) with ESMTP id A9D6F1518D; Fri, 24 Dec 1999 10:25:13 -0800 (PST) (envelope-from kudzu@dnai.com) Received: from dnai.com (dnai-216-15-121-4.cust.dnai.com [216.15.121.4]) by oberon.dnai.com (8.9.3/8.9.3) with ESMTP id KAA00932; Fri, 24 Dec 1999 10:25:04 -0800 (PST) Message-ID: <3863B98A.A3888539@dnai.com> Date: Fri, 24 Dec 1999 10:20:58 -0800 From: Michael Sierchio X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-security@freebsd.org, freebsd-core@freebsd.org Subject: mlockall() not supported (2nd query) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org mlockall() and munlockall() don't appear to be supported on FreeBSD. I consider this to be a security issue -- since maintaining a lot of fine-grained locks is harder than locking the entire heap/stack in memory. This is crucial for generating keys for cryptosystems, which is my current project. One of the stated goals is to be able to repond in the negative to a discovery request for removal and inspection of a hard drive, with the plausible and rational explanation that no information of relevance ever touches magnetic storage media. I am trying to keep FreeBSD in the running, along with Linux and Solaris. I would be happy to assist in any way possible. Please respond. Michael Sierchio -- QUI ME AMET, CANEM MEUM ETIAM AMET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message