From owner-freebsd-current@FreeBSD.ORG  Wed Jun 25 13:49:03 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 43B5037B401
	for <current@freebsd.org>; Wed, 25 Jun 2003 13:49:03 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 81DF944003
	for <current@freebsd.org>; Wed, 25 Jun 2003 13:49:02 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h5PKmeKJ058667;
	Wed, 25 Jun 2003 16:48:40 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)h5PKmesn058664;
	Wed, 25 Jun 2003 16:48:40 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Wed, 25 Jun 2003 16:48:40 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Socketd <db@traceroute.dk>
In-Reply-To: <Pine.NEB.3.96L.1030625164029.58599A-100000@fledge.watson.org>
Message-ID: <Pine.NEB.3.96L.1030625164645.58599D-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: FreeBSD 5.1-Release freezes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2003 20:49:03 -0000


Just FYI, there are actually some "legitimate" situations in which
processes will appear to hang when using MAC.  For example, if you have
MLS or Biba turned on, and revocation support specifically enabled (not
the default), you can see interactive processes appear to hang when they
are interacting with a terminal that is not authorized to receive its
output.  For example, if you change the process labels so that they have
access to top secret data, but your terminal label is set so it is only
cleared for confidential data, the process can't write to the terminal. 

Given that you don't appear to have any policies loaded, that's presumably
not what is going on.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories