From owner-freebsd-hackers  Fri Oct 18 07:49:17 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA27648
          for hackers-outgoing; Fri, 18 Oct 1996 07:49:17 -0700 (PDT)
Received: from saskatchewan.et.byu.edu (saskatchewan.et.byu.edu [128.187.120.25])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA27642
          for <freebsd-hackers@freebsd.org>; Fri, 18 Oct 1996 07:49:06 -0700 (PDT)
Received: by saskatchewan.et.byu.edu; Fri, 18 Oct 1996 08:47:06 -0600 (MDT)
Date: Fri, 18 Oct 1996 08:47:06 -0600 (MDT)
From: gritton@et.byu.edu (Jamie Gritton)
Message-ID: <199610181447.IAA05206@saskatchewan.et.byu.edu>
To: freebsd-hackers@freebsd.org, tech-userlevel@NetBSD.ORG
In-reply-to: <199610180521.AAA08257@Jupiter.Mcs.Net> (message from Karl Denninger on Fri, 18 Oct 1996 00:21:38 -0500 (CDT))
Subject: Re: cvs commit: src/lib/libc/db/hash hash_buf.c
Reply-to: gritton@byu.edu
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Karl Denninger <karl@Mcs.Net> writes:

> If there was a separate "destroy-data" call, that would be ok.  But there
> isn't, and as such the ONLY way to have any security in these dbm routines
> is to have the system enforce it.

   Adding the call seems easy enough, and seems the most elegant solution.

- James Gritton
  jamie@gritton.org