From owner-freebsd-current Tue Sep 1 21:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03193 for freebsd-current-outgoing; Tue, 1 Sep 1998 21:32:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03187 for ; Tue, 1 Sep 1998 21:32:07 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA00418; Tue, 1 Sep 1998 21:28:43 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809012128.VAA00418@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: Bruce Evans , reilly@zeta.org.au, current@FreeBSD.ORG Subject: Re: ELF binaries size In-reply-to: Your message of "Tue, 01 Sep 1998 19:21:07 MST." <199809020221.TAA17213@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 21:28:42 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, how does it enhance security to prevent a program from reading > its own text segment? If a program doesn't want to read its text > segment then it should simply ... not read it. :-) Given that you just steadied the weapon while I blew my foot off, I think I can offer a suggestion as to why it might be awkward to have an execute-only text segment... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message