From owner-cvs-all Wed Apr 7 20:30: 1 1999 Delivered-To: cvs-all@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C73DC1521A; Wed, 7 Apr 1999 20:29:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA24889; Thu, 8 Apr 1999 12:27:33 +0900 (JST) Message-ID: <370C20B2.BD062E4F@newsguy.com> Date: Thu, 08 Apr 1999 12:21:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Greg Lehey Cc: Nick Sayer , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_time.c References: <199904071636.JAA15238@freefall.freebsd.org> <19990408100716.I2142@lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Greg Lehey wrote: > > On Wednesday, 7 April 1999 at 9:36:57 -0700, Nick Sayer wrote: > > nsayer 1999/04/07 09:36:57 PDT > > > > Modified files: > > sys/kern kern_time.c > > Log: > > If securelevel>1, allow the clock to be adjusted negatively only up to > > 1 second prior to the highest the clock has run so far. This allows > > time adjusters like xntpd to do their work, but the worst a miscreant > > can do is "freeze" the clock, not go back in time. > > Does this mean that if somebody accidentally sets the time to the > wrong year, the only thing he can do to fix it is to reboot in > single-user mode? I'm not convinced that this is a gain. What do > people doing Y2K tests do? How about not using securelevel>1 when doing such tests? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message