From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 15:21:42 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A55D16A400 for ; Tue, 30 Jan 2007 15:21:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id DCC8F13C494 for ; Tue, 30 Jan 2007 15:21:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (azwtcf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l0UFLY3c055510; Tue, 30 Jan 2007 16:21:40 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l0UFLYgE055509; Tue, 30 Jan 2007 16:21:34 +0100 (CET) (envelope-from olli) Date: Tue, 30 Jan 2007 16:21:34 +0100 (CET) Message-Id: <200701301521.l0UFLYgE055509@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de In-Reply-To: <20070130140227.26613101832@hk2.uwaterloo.ca> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 30 Jan 2007 16:21:40 +0100 (CET) Cc: Subject: Re: top delay value X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2007 15:21:42 -0000 waldeck@gmx.de wrote: > An unprivileged user could waste all CPU time by setting a low delay > value in top (interactive or via -s). Well, an unprivileged user can achieve the same effect by typing "while :; do :; done". There are a thousand ways to waste CPU time, and there is no way to prevent a user from doing it. > There are other top implementations that use a "secure mode" configuration > which avoids the setting of the delay value for unprivileged users. Really? I don't think such a function has got anything to do with being more "secure". If you want to make top more secure, type "chmod 700 /usr/bin/top". Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Perl is worse than Python because people wanted it worse. -- Larry Wall