From owner-freebsd-hackers  Thu Oct 17 13:05:21 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA25901
          for hackers-outgoing; Thu, 17 Oct 1996 13:05:21 -0700 (PDT)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA25888;
          Thu, 17 Oct 1996 13:05:06 -0700 (PDT)
Received: by gvr.win.tue.nl (8.6.13/1.53)
    id WAA11623; Thu, 17 Oct 1996 22:04:45 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199610172004.WAA11623@gvr.win.tue.nl>
Subject: Re: cvs commit: src/lib/libc/db/hash hash_buf.c
To: thorpej@nas.nasa.gov
Date: Thu, 17 Oct 1996 22:04:45 +0200 (MET DST)
Cc: phk@critter.tfs.com, guido@freebsd.org, freebsd-hackers@freebsd.org,
        tech-userlevel@netbsd.org
In-Reply-To: <199610171900.MAA06276@lestat.nas.nasa.gov> from Jason Thorpe at "Oct 17, 96 12:00:53 pm"
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> bzero'ing a hash buffer is not a complete solution to the problem,
> since the process may contain other potentially sensitive data
> in its address space.  What you really want to do is protect
> the cores.
> 


And what about a user attaching a debugger to a running ftpd...

-Guido