From owner-freebsd-stable Fri Nov 1 19:52:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F5E37B401 for ; Fri, 1 Nov 2002 19:52:23 -0800 (PST) Received: from mx2.cryptohill.net (ns1.cryptohill.net [24.244.145.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E57943E77 for ; Fri, 1 Nov 2002 19:52:23 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (localhost [127.0.0.1]) by mx2.cryptohill.net (Postfix) with ESMTP id 0122D1C8B3; Fri, 1 Nov 2002 22:58:20 -0500 (EST) Date: Fri, 1 Nov 2002 22:49:11 -0500 Subject: rate-limiting uptime went backwards? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: Poul-Henning Kamp To: freebsd-stable@FreeBSD.ORG From: "Jeroen C. van Gelderen" Content-Transfer-Encoding: 7bit Message-Id: <0C73DE87-EE16-11D6-BF9D-000393754B1C@vangelderen.org> X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there any specific reason why the "microuptime went backwards" message is not rate-limited? These messages are rather easy to provoke by the local user tinkering with something as mundane as Java and constitute a nice local DoS attack. -J -- Jeroen C. van Gelderen - jeroen@vangelderen.org - +1 242 357 5115 Incentive Incompatibility To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message