From owner-freebsd-current Tue Sep 1 21:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03854 for freebsd-current-outgoing; Tue, 1 Sep 1998 21:35:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03843 for ; Tue, 1 Sep 1998 21:35:09 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-127.camalott.com [208.229.74.127]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id XAA02018; Tue, 1 Sep 1998 23:35:45 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA03891; Tue, 1 Sep 1998 23:33:52 -0500 (CDT) (envelope-from joelh) Date: Tue, 1 Sep 1998 23:33:52 -0500 (CDT) Message-Id: <199809020433.XAA03891@detlev.UUCP> To: bde@zeta.org.au CC: jdp@polstra.com, reilly@zeta.org.au, current@FreeBSD.ORG In-reply-to: <199809020214.MAA20550@godzilla.zeta.org.au> (message from Bruce Evans on Wed, 2 Sep 1998 12:14:40 +1000) Subject: Re: ELF binaries size From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199809020214.MAA20550@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Is this a security problem? >> I don't think so. Do you? > Maybe if text is supposed to be unreadable. Presently, text must be readable to hold static strings (unless --fwritable-strings is used). Why would being able to read text be a problem? As far as that goes, except in the earlier 'break binary compatibility' thread, why would being able to write to text be a problem? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message