From owner-freebsd-hackers Mon Oct 13 18:20:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08924 for hackers-outgoing; Mon, 13 Oct 1997 18:20:30 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08886; Mon, 13 Oct 1997 18:20:18 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA12696; Tue, 14 Oct 1997 01:19:59 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id DAA13984; Tue, 14 Oct 1997 03:19:54 +0200 (MET DST) Date: Tue, 14 Oct 1997 03:19:54 +0200 (MET DST) Message-Id: <199710140119.DAA13984@bitbox.follo.net> From: Eivind Eklund To: Brian Mitchell CC: petrilli@amber.org, careilly@monoid.cs.tcd.ie, dcarmich@mcs.com, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG In-reply-to: Brian Mitchell's message of Mon, 13 Oct 1997 17:15:55 -0400 (EDT) Subject: Re: C2 Trusted FreeBSD? References: <199710132110.RAA29578@dworkin.amber.org> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Basically, we need to purge all memor when it is allocated, or > > deallocated. > > > yah, when we release something back into a system, we have to bzero() the > contents, or something similar. Something like that already done, AFAIK. Doing anything else would be a serious security break no matter whether we wanted a security branding. Eivind.