From owner-cvs-all Wed Sep 16 11:59:45 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10705 for cvs-all-outgoing; Wed, 16 Sep 1998 11:59:45 -0700 (PDT) (envelope-from owner-cvs-all) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10682; Wed, 16 Sep 1998 11:59:31 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id LAA02037; Wed, 16 Sep 1998 11:58:01 -0700 (PDT) (envelope-from jdp) Message-Id: <199809161858.LAA02037@austin.polstra.com> To: Andrzej Bialecki cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern imgact_elf.c In-reply-to: Your message of "Wed, 16 Sep 1998 08:42:38 +0200." Date: Wed, 16 Sep 1998 11:58:01 -0700 From: John Polstra Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Instead of just the data and stack segments, include all writable > > segments (except memory-mapped devices) in the ELF core file. This > > is really nice. You get access to the data areas of all shared > > libraries, and even to files that are mapped read-write. > ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^ > I wonder if it could be used to gather some security related info out of > core file... I don't believe it opens any security holes of any kind. If you can come up with a specific scenario, by all means let us know. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth