Xref: utzoo alt.bbs:2948 comp.unix.sysv386:433 alt.security:1557
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!usc!randvax!segue!bruce
From: bruce@segue.segue.com (Bruce Adler)
Newsgroups: alt.bbs,comp.unix.sysv386,alt.security
Subject: Re: Protecting against downloads
Message-ID: <3692@segue.segue.com>
Date: 14 Sep 90 19:00:24 GMT
References: <2412@sud509.ed.ray.com> <7772:Sep1408:18:1190@kramden.acf.nyu.edu>
Reply-To: bruce@segue.segue.com (Bruce Adler)
Organization: Segue Software, Inc. - Santa Monica, CA. +1-213-453-2161
Lines: 21

In article <7772:Sep1408:18:1190@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>And what do you do about text images in core files?

Although I'm not familiar with every Unix implementation, the ones I've 
seen don't include the text segment in a core file.  The exception to 
this rule is if you've specially linked your load module to place all of 
the program text in the data segment (i.e.  non-split I+D).  This is 
usually only done when you've a need to modify the text while the 
program is executing via a debugger.  But commercial products aren't 
usually shipped as non-split I+D load modules.  

Core files also don't usually include shared libraries, shared memory 
segments, and/or memory mapped files.  
-- 
bruce@segue.com
ism.isc.com!segue!bruce
aero.org!segue!bruce
-- 
bruce@segue.com
ism.isc.com!segue!bruce
aero.org!segue!bruce