From owner-freebsd-chat Wed Oct 10 6:13:12 2001 Delivered-To: freebsd-chat@freebsd.org Received: from be-well.ilk.org (lowellg.ne.mediaone.net [24.147.184.128]) by hub.freebsd.org (Postfix) with ESMTP id 9FEFE37B401 for ; Wed, 10 Oct 2001 06:13:09 -0700 (PDT) Received: (from lowell@localhost) by be-well.ilk.org (8.11.6/8.11.4) id f9ADCuI20380; Wed, 10 Oct 2001 09:12:56 -0400 (EDT) (envelope-from lowell) To: GB Clark II Cc: freebsd-chat@FreeBSD.ORG Subject: Re: code density vs readability References: <9ptk3o$14kg$1@FreeBSD.csie.NCTU.edu.tw> <44d73xt0y9.fsf@lowellg.ne.mediaone.net> <0110090955220A.07185@prime.vsservices.com> From: Lowell Gilbert Date: 10 Oct 2001 09:12:56 -0400 In-Reply-To: GB Clark II's message of "Tue, 9 Oct 2001 09:55:22 -0500" Message-ID: <448zejljtz.fsf@lowellg.ne.mediaone.net> Lines: 14 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org GB Clark II writes: > There was at one time a hole in emacs that would let you write system files. > This was about 8 or 9 years ago I belive. Impossible. emacs runs with user privileges, so no hole in it could have any effect like this. The original concern, about whether emacs could have malicious code shipped with it, is more realistic. I think it's not worth worrying about, because there really are more eyes on the code, on a more regular basis, than the original poster realized. - Lowell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message