Date: Fri, 8 Jan 1999 16:51:58 -0600 (CST) From: Joe Greco <jgreco@solaria.sol.net> To: stenn@whimsy.udel.edu Cc: current@FreeBSD.ORG Subject: Re: 3.0R and NTP, security changes in settimeofday Message-ID: <199901082251.QAA01092@aurora.sol.net> In-Reply-To: <o4aeztqxwr.fsf@whimsy.udel.edu> from "stenn@whimsy.udel.edu" at "Jan 8, 99 04:04:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> xntp 3.4e is Horribly Ancient and massively buggy. There is a port of > ntp-4.0.73something in the ports collection, but the latest release > (4.0.90h or so) should work fine out of the box. Yeah, well, it came with the system... which is why I posted my gripe mainly at the FreeBSD lists. :-) But I thought the NTP people would like to know that such a restriction is now being imposed by a modern operating system. Unfortunately, I maintain over a hundred systems, and running around to custom-install NTP on each just isn't an option. I don't think that it was completely unreasonable behaviour by NTP anyways, since at the time, I believe that the securelevel restriction did not exist. However, today, I'd like to see the FreeBSD people either consider a workaround, or upgrading and verifying that a newer NTP works properly. If you're going to prevent the system from changing the clock backwards, it seems only reasonable to make sure that the time daemon can live with that. Thanks for the note, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901082251.QAA01092>