From owner-freebsd-security@FreeBSD.ORG  Thu Sep 22 11:40:36 2005
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
X-Original-To: freebsd-security@freebsd.org
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C8B6516A41F
	for <freebsd-security@freebsd.org>;
	Thu, 22 Sep 2005 11:40:36 +0000 (GMT)
	(envelope-from borjamar@sarenet.es)
Received: from sollube.sarenet.es (mx1.sarenet.es [194.30.0.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB9443D46
	for <freebsd-security@freebsd.org>;
	Thu, 22 Sep 2005 11:40:36 +0000 (GMT)
	(envelope-from borjamar@sarenet.es)
Received: from [127.0.0.1] (borja.sarenet.es [192.148.167.77])
	by sollube.sarenet.es (Postfix) with ESMTP id 4F2B11921;
	Thu, 22 Sep 2005 13:40:35 +0200 (CEST)
In-Reply-To: <200509221124.j8MBOkMM017056@the-macgregors.org>
References: <200509221124.j8MBOkMM017056@the-macgregors.org>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1C5552E8-3E4C-41D4-80F4-7AAA6FD3EF7D@sarenet.es>
Content-Transfer-Encoding: 7bit
From: Borja Marcos <borjamar@sarenet.es>
Date: Thu, 22 Sep 2005 13:41:18 +0200
To: Rob MacGregor <freebsd.macgregor@blueyonder.co.uk>
X-Mailer: Apple Mail (2.734)
Cc: freebsd-security@freebsd.org
Subject: Re: Mounting filesystems with "noexec"
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2005 11:40:37 -0000

> As long as you can disable/limit the logging.  One very nasty  
> "attack" would be
> to loop trying to run a binary.  Blow your logging partition.   
> Somebody could
> then use that to do other things that would normally be logged,  
> safe in the
> knowledge that their activities wouldn't be logged.
>
> I've seen systems brought to their knees by similar well  
> intentioned logging
> activities.  It's not pretty :)

     That's out of the question, of course :)

     A sysctl could control it. Anyway, the same can happen with  
zillions of logged events.




     Borja.