From owner-freebsd-questions@FreeBSD.ORG Wed Apr 16 16:28:44 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 894DD37B401; Wed, 16 Apr 2003 16:28:44 -0700 (PDT) Received: from kurdistan.ath.cx (adsl-64-169-155-173.dsl.chic01.pacbell.net [64.169.155.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC38F43FD7; Wed, 16 Apr 2003 16:28:43 -0700 (PDT) (envelope-from sereciya@kurdistan.ath.cx) Received: from kurdistan.ath.cx (ns1 [127.0.0.1]) by kurdistan.ath.cx (8.12.8/8.12.6) with ESMTP id h3GNSj04060054; Wed, 16 Apr 2003 16:28:45 -0700 (PDT) (envelope-from sereciya@kurdistan.ath.cx) Received: (from sereciya@localhost) by kurdistan.ath.cx (8.12.8/8.12.6/Submit) id h3GNSjx6060053; Wed, 16 Apr 2003 16:28:45 -0700 (PDT) Date: Wed, 16 Apr 2003 16:28:44 -0700 From: =?unknown-8bit?Q?S=EAr=EAciya_Kurdistan=EE?= To: freebsd-questions@freebsd.org Message-ID: <20030416232844.GF58471@kurdistan.ath.cx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eDB11BtaWSyaBkpc" Content-Disposition: inline Subject: FreeBSD Memory Pages Not Locked? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2003 23:28:44 -0000 --eDB11BtaWSyaBkpc Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I recently installed "gpnupg" from the ports collection and upon running it (after the key generation), I found myself seeing the following error: gpg: Warning: using insecure memory! ... Those of you who are impatient and think that this is a gpg &| port specific problem, please be patient and read on ... from: http://www.gnupg.org/documentation/faqs.html#q6.1 Here's what the GPG FAQ says: "6.1) Why do I get "gpg: Warning: using insecure memory! On many systems this program should be installed as setuid. This is necessary to lock memory pages. Locking memory pages prevents the operating system from writing them to disk and thereby keeping your secret keys really secret. If you get no warning message about insecure memory your operating system supports locking without being root. The program drops root privileges as soon as locked memory is allocated." I would like to know if FreeBSD does indeed lack the functionality to lock memory pages, does it? If not... how come then? Is this not something important, especially from a security standpoint? And if it does... how come I recieved this error then? Thanks in advance to anyone and everyone who may reply/post useful comments & suggestions..., thank you! --$=EAr=EAciya Kurdistan=EE +--------------------------------------------------------------+ | Welat xwe ava nake, dest bidin hevdu, pist nedin tu dijmin=EE | | Riya azadiy=EA ne h=EAsan e, h=EAviya xwe bernedin, dema me | | n=EAz=EEk e. | | | | Hevalt=EE bi kes=EAn du r=FB nekin, hevalt=EE bi hevdu ra bikin | | Ne ji hevaltiya wan kes=EAn p=EAxwas =FB r=FB dir=EAj, ne bi wan | | kes=EAn xw=EEnperest, ne j=EE ji y=EAn din. | | | | -$=EAr=EAciya Kurdistan=EE | +--------------------------------------------------------------+ translation provided on request: sereciya at kurdistan.ath.cx --eDB11BtaWSyaBkpc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+necs2rX+NTHoe2QRAh19AKCEBu6B3nrToJeivSkL/KotZasGcgCfQqUM VWdiCDg0wq6EhfNx/LDzU2g= =/iEK -----END PGP SIGNATURE----- --eDB11BtaWSyaBkpc--