From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: some #s
In-Reply-To: <200306050320.h553KG516675@augusta.math.psu.edu>
Message-ID: <Pine.LNX.4.33.0306050630000.9676-100000@einstein.ssz.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Date: Thu,  5 Jun 2003 06:33:08 -0500
Topicbox-Message-UUID: c52c4ad6-eacb-11e9-9e20-41e7f4b1d025


On Wed, 4 Jun 2003, Dan Cross wrote:

> I have no idea what Choate means by ``memory leakage.''

<sigh>

> Most sytems have well defined semantics for returning memory to a
> ``known state'' after a process exits,

And Unix and Microsoft (among many others) are known not to do that well.
Not to mention the many times programmers just don't do 'the right thing'.

Some time reading security literature about such holes will be quite
elucidating. Try starting with "Applied Cryptography".


 --
    ____________________________________________________________________

      We are all interested in the future for that is where you and I
      are going to spend the rest of our lives.

                              Criswell, "Plan 9 from Outer Space"

      ravage@ssz.com                            jchoate@open-forge.org
      www.ssz.com                               www.open-forge.org
    --------------------------------------------------------------------