Time to update the leapsecond file / 2014-12-29

I recently upgraded ntpd due to the vulnerabilities found in ntpd prior to version 4.2.8. This version is also a bit better in error logging, and I started seeing in the logs:

Dec 21 20:53:06 ritchie ntpd[6918]: leapsecond file ('/etc/ntp/leap-seconds.3535228800'): loaded, expire=2014-12-28T00:00Z ofs=35 (no entries after build date)
Dec 21 20:53:06 ritchie ntpd[6918]: leapsecond file ('/etc/ntp/leap-seconds.3535228800'): will expire in less than 7 days
Dec 22 20:53:06 ritchie ntpd[6918]: leapsecond file ('/etc/ntp/leap-seconds.3535228800'): will expire in less than 6 days
Dec 23 20:53:06 ritchie ntpd[6918]: leapsecond file ('/etc/ntp/leap-seconds.3535228800'): will expire in less than 5 days

Dec 28 00:53:06 ritchie ntpd[6918]: leapsecond file ('/etc/ntp/leap-seconds.3535228800'): will expire in less than one day

So I followed the documentation in ConfiguringNTP: 6.14. Using the NIST Leap Second File and upgraded to leap-seconds.3644438400 which now loads fine:

Dec 29 11:25:29 ritchie ntpd[28281]: leapsecond file ('/etc/ntp/leap-seconds.3644438400'): good hash signature
Dec 29 11:25:29 ritchie ntpd[28281]: leapsecond file ('/etc/ntp/leap-seconds.3644438400'): loaded, expire=2015-06-28T00:00Z ofs=35 (no entries after build date)