Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 28 Mar 2001 08:53:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 28 Mar 2001 08:53:46 -0500 Received: from james.kalifornia.com ([208.179.59.2]:34420 "EHLO james.kalifornia.com") by vger.kernel.org with ESMTP id ; Wed, 28 Mar 2001 08:53:35 -0500 Message-ID: <3AC17BB1.8000201@kalifornia.com> Date: Tue, 27 Mar 2001 21:50:41 -0800 From: Ben Ford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i586; en-US; 0.8.1) X-Accept-Language: en MIME-Version: 1.0 To: jesse@cats-chateau.net CC: Shawn Starr , Matti Aarnio , linux-kernel@vger.kernel.org Subject: Re: Disturbing news.. References: <01032806093901.11349@tabby> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1061 Lines: 28 Jesse Pollard wrote: > On Wed, 28 Mar 2001, Shawn Starr wrote: > >> Well, why can't the ELF loader module/kernel detect or have some sort of >> restriction on modifying other/ELF binaries including itself from changing >> the Entry point? >> >> There has to be a way stop this. WHY would anyone want to modify the entry >> point anyway? (there may be some reasons but I really dont know what). >> Even if it's user level, this cant affect files with root permissions >> (unless root is running them or suid). >> >> Any idea? > > > Sure - very simple. If the execute bit is set on a file, don't allow > ANY write to the file. This does modify the permission bits slightly > but I don't think it is an unreasonable thing to have. > What a pain in the ass when you are writing / updating a shell script . . . . - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/