From owner-freebsd-chat@FreeBSD.ORG  Sun Jul 12 22:30:03 2009
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Delivered-To: chat@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2A771106566C
	for <chat@freebsd.org>; Sun, 12 Jul 2009 22:30:03 +0000 (UTC)
	(envelope-from jcw@highperformance.net)
Received: from mx1.highperformance.net (s4.stradamotorsports.com
	[64.81.163.122])
	by mx1.freebsd.org (Postfix) with ESMTP id DBD578FC18
	for <chat@freebsd.org>; Sun, 12 Jul 2009 22:30:02 +0000 (UTC)
	(envelope-from jcw@highperformance.net)
Received: from [192.168.1.191] ([192.168.1.191])
	by mx1.highperformance.net (8.14.3/8.14.3) with ESMTP id n6CMBNIG001974
	for <chat@freebsd.org>; Sun, 12 Jul 2009 15:11:23 -0700 (PDT)
	(envelope-from jcw@highperformance.net)
Message-ID: <4A5A5F8B.4030909@highperformance.net>
Date: Sun, 12 Jul 2009 15:11:23 -0700
From: "Jason C. Wells" <jcw@highperformance.net>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: chat@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.4 required=2.5 tests=ALL_TRUSTED autolearn=failed
	version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	s4.stradamotorsports.com
Cc: 
Subject: Whitelist Before Execution
X-BeenThere: freebsd-chat@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Non technical items related to the community
	<freebsd-chat.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chat>
List-Post: <mailto:freebsd-chat@freebsd.org>
List-Help: <mailto:freebsd-chat-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jul 2009 22:30:03 -0000

Is there a method by which we can check the consistency of an executable 
or library prior to trusting it for execution?  For example, if the file 
doesn't exist in the list of trusted files or the checksums do not match 
then do not allow execution and write a warning message to the log.  I 
could do this manually with existing features like mtree.  It would be 
nice if the system could do it for me.

Later,
Jason