Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264231AbTEGVPI (ORCPT ); Wed, 7 May 2003 17:15:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264232AbTEGVPI (ORCPT ); Wed, 7 May 2003 17:15:08 -0400 Received: from 34.mufa.noln.chcgil24.dsl.att.net ([12.100.181.34]:62196 "EHLO tabby.cats.internal") by vger.kernel.org with ESMTP id S264231AbTEGVPG (ORCPT ); Wed, 7 May 2003 17:15:06 -0400 Content-Type: text/plain; charset=US-ASCII From: Jesse Pollard To: petter wahlman , root@chaos.analogic.com Subject: Re: The disappearing sys_call_table export. Date: Wed, 7 May 2003 16:27:16 -0500 X-Mailer: KMail [version 1.2] Cc: Linux kernel References: <1052321673.3727.737.camel@badeip> <1052330844.3739.840.camel@badeip> In-Reply-To: <1052330844.3739.840.camel@badeip> MIME-Version: 1.0 Message-Id: <03050716271600.07468@tabby> Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 917 Lines: 21 On Wednesday 07 May 2003 13:07, petter wahlman wrote: > On Wed, 2003-05-07 at 18:59, Richard B. Johnson wrote: > [snip] > > The same way you would force a virus to not be statically linked. > > You make sure that only programs that interface with the kernel > > thorugh your hooks can run on that particular system. > > Can you please elaborate. > How would you implement the access control without modifying the > respective syscalls or the system_call(), and would you'r > solution be possible to implement run time? Access control is available via the LSM, with well defined interfaces. If that is what you want to control, then use the LSM, and not the syscall table. - 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/