Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261347AbUDHNLb (ORCPT ); Thu, 8 Apr 2004 09:11:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261421AbUDHNLa (ORCPT ); Thu, 8 Apr 2004 09:11:30 -0400 Received: from faui3es.informatik.uni-erlangen.de ([131.188.33.16]:5556 "EHLO faui3es.informatik.uni-erlangen.de") by vger.kernel.org with ESMTP id S261347AbUDHNL2 (ORCPT ); Thu, 8 Apr 2004 09:11:28 -0400 Date: Thu, 8 Apr 2004 15:11:17 +0200 From: Martin Waitz To: Sergiy Lozovsky Cc: Timothy Miller , Horst von Brand , linux-kernel@vger.kernel.org Subject: Re: kernel stack challenge Message-ID: <20040408131116.GO27401@admingilde.org> Mail-Followup-To: Sergiy Lozovsky , Timothy Miller , Horst von Brand , linux-kernel@vger.kernel.org References: <407335B3.1070200@techsource.com> <20040406231734.92421.qmail@web40505.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aEJuoWUqNbltyjQQ" Content-Disposition: inline In-Reply-To: <20040406231734.92421.qmail@web40505.mail.yahoo.com> User-Agent: Mutt/1.3.28i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-PGP-Fingerprint: B21B 5755 9684 5489 7577 001A 8FF1 1AC5 DFE8 0FB2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1483 Lines: 45 --aEJuoWUqNbltyjQQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi :) On Tue, Apr 06, 2004 at 04:17:34PM -0700, Sergiy Lozovsky wrote: > What? Give an example. I want something high level, so > Forth will not do. Sure, encapsulation is needed, to > protect kernel from pointer errors and so on. who says that the language that's used by your policy administrator is the same as the language interpreted by the kernel? let your administrator write his policy in java/lisp or whatever, but compile this policy into an easy to interpret and safe bytecode. --=20 CU, / Friedrich-Alexander University Erlangen, Germany Martin Waitz // Department of Computer Science 12 _________ ______________/// - - - - - - - - - - - - - - - - - - - - /// dies ist eine manuell generierte mail, sie beinhaltet // tippfehler und ist auch ohne grossbuchstaben gueltig. / --aEJuoWUqNbltyjQQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAdU9zj/Eaxd/oD7IRAhg3AJ9RPv6TPRljNHKQfM1p33VTOhnCcQCfaigr /Wb3EQluaS0W/rqtMjjXI1o= =a8dR -----END PGP SIGNATURE----- --aEJuoWUqNbltyjQQ-- - 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/