From owner-freebsd-stable Fri Nov 1 22:27:59 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 1537637B401 for ; Fri, 1 Nov 2002 22:27:58 -0800 (PST) Received: from mx2.cryptohill.net (ns1.cryptohill.net [24.244.145.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 774D643E4A for ; Fri, 1 Nov 2002 22:27:57 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (localhost [127.0.0.1]) by mx2.cryptohill.net (Postfix) with ESMTP id 16DBD1C891; Sat, 2 Nov 2002 01:33:55 -0500 (EST) Date: Sat, 2 Nov 2002 01:28:42 -0500 Subject: Re: rate-limiting uptime went backwards? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: freebsd-stable@FreeBSD.ORG To: Peter Hoskin From: "Jeroen C. van Gelderen" In-Reply-To: <20021102163558.S301-100000@extortion.peterh.dropbear.id.au> Message-Id: <54AF0182-EE2C-11D6-AA9F-000393754B1C@vangelderen.org> Content-Transfer-Encoding: 7bit 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 On Saturday, Nov 2, 2002, at 00:37 US/Eastern, Peter Hoskin wrote: > Those messages are usually due to a faulty system clock. Generally, > when > you generate a bit of load these messages will appear. The reason why > they > aren't rate limited is they are an important kernel message. Thanks for the explanation. What I do not understand still is how DoSing my machine with these messages is going to be beneficial. It is bad enough that my clock is not operating correctly so I can do without kernel log messages grinding the machine to a halt. My question stands: how is a message once a second going to be less noticeable than a thousand per second? -J > > Regards, > Peter Hoskin > > On Fri, 1 Nov 2002, Jeroen C. van Gelderen wrote: > >> 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 >> > > -- Jeroen C. van Gelderen - jeroen@vangelderen.org - +1 242 357 5115 "All that is necessary for evil to triumph is for good men to do nothing." -- Edmund Burke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message