It's me again with my annual NTP whinge. https://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075580.html https://lists.freebsd.org/pipermail/freebsd-stable/2014-September/079830.html Here we are at the start of another release cycle and 10-STABLE still includes (patched) ntp 4.2.4p8 software that was released in December 2009. - ntp 4.2.6 superseded 4.2.4 and was also released in December 2009. - ntp 4.2.8 superseded 4.2.6 and was released in December 2014. Will 10.2 be released with a version of ntp that is two generations old and that has been legacy since December 2009? I am really pleased to see that there has been some recent activity with respect to ntp in -CURRENT, and that the latest point release (4.2.8p3) has actually been imported. Is there any likelihood of this being MFC'd before releng/10.2 is branched? Thank you for your patience with me, and thank you to committers who are working in this space but perhaps not with an eye to -STABLE. I just think it's really sad that we are shipping very old ntp software with lots of patches when a current release is available. I also note that phk@ was working on an ntp client which he hoped to offer as a replacement but that is presumably not ready yet. I also note that we have current versions of ntp available in ports; but I'm talking about what we ship in the base system. -- John Marshall -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150711/37fbbeb4/attachment.bin>
John Marshall <john.marshall at riverwillow.com.au> wrote:> I also note that phk@ was working on an ntp client which he hoped to > offer as a replacement but that is presumably not ready yet. I also > note that we have current versions of ntp available in ports; but I'm > talking about what we ship in the base system.I realise you are talking about stable software in base, but for info, phk's replacement is called 'ntimed' and can be found on github, and also in /usr/ports/net/ntimed/ - it's unfinished and we are not advised to run it on production systems, but living dangerously, I've been running it on 4 servers for a few months with no issues (although I had to make some 'glue' changes to make it stable.) cheers, Jamie
Hi
As head already has 4.2.8 p3 in tree, MFCing this before BETA2 would be
nice because...
*At least, authorized open stratum 1 by NICT supports only 4.2.6 or
later for configuration line (in ntp.conf) like below.
pool ntp.nict.jp
*This type of configuration is NOT supported by 4.2.4 branch.
4.2.4 still works for now, but NOT supported by NICT.
*JST (Japanese Standard Time) is maintained by NICT.
http://www.nict.go.jp/JST/JST_E.html
http://www2.nict.go.jp/aeri/sts/tsp/PubNtp/index-e.html
So syncing to their NTP server by officially supported way with BASE
should be nice for Japanese users, I think.
Of course, ports has 4.2.8p3. But head also has it. The best way would
be MFCing. Is there any problem (with GPS, authenticate, etc.)?
On Sat, 11 Jul 2015 09:58:11 +1000
John Marshall <john.marshall at riverwillow.com.au> wrote:
> It's me again with my annual NTP whinge.
>
> https://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075580.html
>
https://lists.freebsd.org/pipermail/freebsd-stable/2014-September/079830.html
>
> Here we are at the start of another release cycle and 10-STABLE still
> includes (patched) ntp 4.2.4p8 software that was released in December
> 2009.
> - ntp 4.2.6 superseded 4.2.4 and was also released in December 2009.
> - ntp 4.2.8 superseded 4.2.6 and was released in December 2014.
>
> Will 10.2 be released with a version of ntp that is two generations old
> and that has been legacy since December 2009?
>
> I am really pleased to see that there has been some recent activity with
> respect to ntp in -CURRENT, and that the latest point release (4.2.8p3)
> has actually been imported. Is there any likelihood of this being
> MFC'd before releng/10.2 is branched?
>
> Thank you for your patience with me, and thank you to committers who are
> working in this space but perhaps not with an eye to -STABLE. I just
> think it's really sad that we are shipping very old ntp software with
> lots of patches when a current release is available.
>
> I also note that phk@ was working on an ntp client which he hoped to
> offer as a replacement but that is presumably not ready yet. I also
> note that we have current versions of ntp available in ports; but I'm
> talking about what we ship in the base system.
>
> --
> John Marshall
--
?? ?? [Tomoaki AOKI]
junchoon at dec.sakura.ne.jp
MXE02273 at nifty.com
On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:> It's me again with my annual NTP whinge.The answer to the perennial "will release $foo ship with old / insecure / otherwise deficient $bar?" is still "install $bar from ports". -- Chris Nehren