9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: some #s
Date: Thu,  5 Jun 2003 06:33:08 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0306050630000.9676-100000@einstein.ssz.com> (raw)
In-Reply-To: <200306050320.h553KG516675@augusta.math.psu.edu>


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
    --------------------------------------------------------------------




  reply	other threads:[~2003-06-05 11:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  4:21 [9fans] " ron minnich
2003-06-04  4:45 ` andrey mirtchovski
2003-06-04 14:31   ` ron minnich
2003-06-04 11:27 ` C H Forsyth
2003-06-04 14:39   ` ron minnich
2003-06-04 15:39     ` andrey mirtchovski
2003-06-04 21:20     ` northern snowfall
2003-06-04 23:06       ` [9fans] " Jim Choate
2003-06-05  0:24         ` northern snowfall
2003-06-05  3:20           ` Dan Cross
2003-06-05 11:33             ` Jim Choate [this message]
2003-06-05 22:41               ` Dan Cross
2003-06-05 23:06                 ` Jim Choate
2003-06-06  0:25                   ` David Presotto
2003-06-06  1:08                     ` Dan Cross
2003-06-06  1:19                       ` David Presotto
2003-06-06  3:58                         ` northern snowfall
2003-06-06  3:41                           ` ron minnich
2003-06-06 11:36                             ` Jim Choate
2003-06-06  4:04                           ` northern snowfall
2003-06-06 12:01                         ` Jim Choate
2003-06-06 12:02                           ` David Presotto
2003-06-06  1:21                       ` boyd, rounin
2003-06-06  2:24                       ` Russ Cox
2003-06-06  3:15                         ` Dan Cross
2003-06-06  4:17                           ` northern snowfall
2003-06-06  3:33                             ` Dan Cross
2003-06-06  4:45                               ` northern snowfall
2003-06-06  5:46                                 ` Dan Cross
2003-06-06  9:48                                   ` northern snowfall
2003-06-06  3:51                             ` boyd, rounin
2003-06-06 15:45                     ` Jack Johnson
2003-06-05  3:20       ` [9fans] " ron minnich
2003-06-04 16:46 ` jmk
2003-06-04 22:38   ` ron minnich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0306050630000.9676-100000@einstein.ssz.com \
    --to=ravage@einstein.ssz.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).