Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!lll-winken!sun-barr!ccut!titcca!anprda!akira
From: akira@atson.asahi-np.co.jp (Akira Takiguchi)
Newsgroups: comp.lang.c
Subject: Re: validity of free() on later pointer operations
Message-ID: <925@anprda.atson.asahi-np.co.jp>
Date: 12 Jul 90 04:38:40 GMT
References: <1990Jul3.185032.8434@indetech.com> <1990Jul03.233255.2616@virtech.uucp> <1956@runxtsa.runx.oz.au>
Reply-To: akira@anprda.atson.asahi-np.co.jp (Akira Takiguchi)
Organization: ATSON, Inc.
Lines: 13

In article <1956@runxtsa.runx.oz.au> edward@runxtsa.runx.oz.au (Edward Birch) writes:
|I quote the manual here:
|	The argument to "free" is a pointer to a block previosly allocated
|	by "malloc"; after "free" is performed this space is made available
|	for further allocation, but its contents are left undisturbed.
|
|The above manual entry implies that the following is correct although
|*strongly* unadvisible.

       It seems to me that the manual warns about the possibility of a
  security breach when you leave sensitive data in the free'ed space.
-- 
                                       Akira Takiguchi @ ATSON, Inc.