Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261545AbUCDIfs (ORCPT ); Thu, 4 Mar 2004 03:35:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261563AbUCDIfs (ORCPT ); Thu, 4 Mar 2004 03:35:48 -0500 Received: from fw.osdl.org ([65.172.181.6]:59520 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S261545AbUCDIfr (ORCPT ); Thu, 4 Mar 2004 03:35:47 -0500 Date: Thu, 4 Mar 2004 00:35:46 -0800 From: Chris Wright To: Michael Frank Cc: kernel mailing list Subject: Re: How to black list shared libraries and executable Message-ID: <20040304003546.U22989@build.pdx.osdl.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mhf@linuxmail.org on Thu, Mar 04, 2004 at 03:10:34PM +0800 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 625 Lines: 17 * Michael Frank (mhf@linuxmail.org) wrote: > Just wondering on how to build a kernel-level facility which would > require shared libraries and executables to be "keyed" or even > "signed" to run on linux. Take a look at Cryptomark or DigSig. They at least cover the executables bit. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - 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/