From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 18 18:35:50 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71AA216A4CE for ; Tue, 18 Nov 2003 18:35:50 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A9F43FB1 for ; Tue, 18 Nov 2003 18:35:49 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 04D49653D4; Wed, 19 Nov 2003 02:35:48 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 53967-01-2; Wed, 19 Nov 2003 02:35:47 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 82289653D8; Wed, 19 Nov 2003 02:35:47 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 594791B; Wed, 19 Nov 2003 02:35:33 +0000 (GMT) Date: Wed, 19 Nov 2003 02:35:33 +0000 From: Bruce M Simpson To: Rayson Ho Message-ID: <20031119023533.GB90922@saboteur.dek.spc.org> Mail-Followup-To: Rayson Ho , freebsd-hackers@freebsd.org References: <20031119003133.18473.qmail@web11404.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031119003133.18473.qmail@web11404.mail.yahoo.com> cc: freebsd-hackers@freebsd.org Subject: Re: "secure" file flag? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 02:35:50 -0000 On Tue, Nov 18, 2003 at 04:31:32PM -0800, Rayson Ho wrote: > I am wondering if it is useful to have a "secure" file flag?? ... > e.g. when deleting a "secure" file, the OS will overwrite the file with > random data. I've got patches somewhere for zeroing out memory mappings in this way, but they are incomplete. :-( BMS