Date: Thu, 26 Aug 1999 06:39:55 +1000 From: Greg Black <gjb-freebsd@gba.oz.au> To: "H. Eckert" <ripley@nostromo.in-berlin.de> Cc: freebsd-security@FREEBSD.ORG Subject: Re: Securelevel 3 and setting time Message-ID: <19990825203955.645.qmail@alice.gba.oz.au> In-Reply-To: <19990824235908.B70739@server.nostromo.in-berlin.de> of Tue, 24 Aug 1999 23:59:08 %2B0200 References: <19990822112923.6666.qmail@alice.gba.oz.au> <19990822194140.623D211@woodstock.monkey.net> <19990824235908.B70739@server.nostromo.in-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> The main question we haven't come to a conclusion so far is > what action should(n't) be taken as a possible solution for the > "rarely synched clock in an elevated secure level" scenario. > > - Loosen security and allow for bigger time jumps ? > - Forcing the admin to sync the clock more often ? > - Enabling ntpdate to distribute the time adjustments into > several smaller jumps instead of a big leap ? Surely the simple solution here is to build ntpdate so that it always uses adjtime(2). -- Greg Black -- <gjb@acm.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990825203955.645.qmail>