From owner-freebsd-ports Thu Jan 31 3:12:13 2002 Delivered-To: freebsd-ports@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id C5D5237B400 for ; Thu, 31 Jan 2002 03:12:07 -0800 (PST) Received: from there (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id A15F63FC05; Thu, 31 Jan 2002 12:12:03 +0100 (CET) Content-Type: text/plain; charset="iso-8859-15" From: Miguel Mendez Organization: Energy HQ To: "Thomas E. Zander" , ports@freebsd.org Subject: Re: gnupg insecure memory Date: Thu, 31 Jan 2002 12:11:31 +0100 X-Mailer: KMail [version 1.3.2] References: <20020131110513.GE46820@f113.hadiko.de> In-Reply-To: <20020131110513.GE46820@f113.hadiko.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020131111203.A15F63FC05@energyhq.homeip.net> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thursday 31 January 2002 12:05, Thomas E. Zander wrote: Hi there, > Hi, > > I have now upgraded to 4.5-RELEASE, all applications built from > scratch, and gnupg tells about "using insecure memory". > > Normally, this happens only if the gpg binary is not setuid root. > But it is, and this message appears to root, too. > > Does anybody else see this behavior and has an idea of what's going on > there? This is totally normal behavior. Insercure memory means that the pages that contain you private key data might get swapped. In order to avoid this they need to be marked as non-swappable (don't remember the exact term, sorry) and only setuid programs can do it if you run them as a normal user. Not a big issue I think. Cheers, -- Miguel Mendez - flynn@energyhq.homeip.net Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message