From owner-freebsd-security  Sun Jun 14 13:27:13 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA23839
          for freebsd-security-outgoing; Sun, 14 Jun 1998 13:27:13 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from adk.gr (COREDUMP.CIS.UPENN.EDU [158.130.6.141])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23816
          for <security@freebsd.org>; Sun, 14 Jun 1998 13:27:05 -0700 (PDT)
          (envelope-from angelos@dsl.cis.upenn.edu)
Received: from dsl.cis.upenn.edu ([198.223.41.41])
	by adk.gr (8.8.8/8.8.5) with ESMTP id QAA16124
	for <security@freebsd.org>; Sun, 14 Jun 1998 16:26:36 -0400 (EDT)
Message-Id: <199806142026.QAA16124@adk.gr>
To: security@FreeBSD.ORG
Subject: Re: bsd securelevel patch question
Date: Sun, 14 Jun 1998 16:20:41 EDT
From: "Angelos D. Keromytis" <angelos@dsl.cis.upenn.edu>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I think the right question is to ask "what use are securelevels ?"
They're ultimately flawed, so what's the point in trying to fix such
bugs ? Is anyone really using securelevels anyway ?
-Angelos

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message