[chrony-users] Re: chrony-1.31.1 released (security)

On Tue, Apr 07, 2015 at 04:56:05PM +0200, Miroslav Lichvar wrote: > Security fixes > -- > * Protect authenticated symmetric NTP associations against DoS attacks > (CVE-2015-1799) This vulnerability is now tracked as CVE-2015-1853, separately from CVE-2015-1799 which was created for

[chrony-users] chrony-2.0-pre2 released (security)

The second prerelease for chrony-2.0 is now available. It includes the three security fixes from 1.31.1, and also some new bug fixes and improvements. The sources can be downloaded here: http://download.tuxfamily.org/chrony/chrony-2.0-pre2.tar.gz MD5 and SHA1 sums:

[chrony-users] chrony-1.31.1 released (security)

chrony-1.31.1 is now available. It fixes three security vulnerabilities. The sources can be downloaded here: http://download.tuxfamily.org/chrony/chrony-1.31.1.tar.gz MD5 and SHA1 sums: 01e54c63d09a310f30c4e399f18499df chrony-1.31.1.tar.gz 8e92871e164dad89b315a5dda99d94ff7b31770a

Re: [chrony-users] Automotive usage of chronyd

Thanks a lot, now it works ! Best regards, Olivier On Tue, Apr 7, 2015 at 12:56 PM, Miroslav Lichvar wrote: > On Tue, Apr 07, 2015 at 12:04:33PM +0200, Olivier Delbeke wrote: > > The tv values are what I send : it's the timestamp received from the GPS > > sensor, in local

Re: [chrony-users] Automotive usage of chronyd

On Tue, Apr 07, 2015 at 12:04:33PM +0200, Olivier Delbeke wrote: > The tv values are what I send : it's the timestamp received from the GPS > sensor, in local time (created using mktime()). > > My chrony.conf : >refclock SOCK /tmp/chrony.gps.sock >makestep 1000 10 > > The code that fills

Re: [chrony-users] Automotive usage of chronyd

Hi all, I think I completely misunderstood what I have to send to chronyd. All my samples are still rejected. The system's date/time is Jan 1, 1970, 00:18. Every second, I get the correct (UTC) time from the GPS sensor and send it to chronyd. Here are my logs : 1970-01-01T00:18:02Z