From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16476 invoked by alias); 21 Jul 2003 01:35:10 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 16468 invoked from network); 21 Jul 2003 01:35:10 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by sources.redhat.com with SMTP; 21 Jul 2003 01:35:10 -0000 Received: from fleche.redhat.com (tf0005.peakpeak.com [204.144.239.5]) by gash2.peakpeak.com (8.9.3/8.9.3.1) with ESMTP id TAA13725; Sun, 20 Jul 2003 19:35:08 -0600 Received: by fleche.redhat.com (Postfix, from userid 1000) id 3DEB24F8389; Sun, 20 Jul 2003 19:25:24 -0600 (MDT) To: Mauve News Group Subject: security test From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Sign my PETITION. Date: Mon, 21 Jul 2003 01:35:00 -0000 Message-ID: <878yqsacxo.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q3/txt/msg00002.txt.bz2 Folks, I just checked in the first Mauve security test. I've added a new dumb-ish (see below) SecurityManager to the test harness. I've also changed SimpleTestHarness to uninstall the security manager after each test runs. In all likelihood this is not the best way to do security tests. I'm still learning about this area; luckily there aren't many tests yet, so we can change things around to be better as needed. I'd like to see more security tests go in to Mauve. In particular the ideal would be to test every check required by the spec. Tom