top | item 9049945

Authenticated TLS “contraints” in ntpd(8)

68 points| protomyth | 11 years ago |marc.info | reply

7 comments

order
[+] handsomeransoms|11 years ago|reply
This is very similar to the functionality provided by tlsdate (https://github.com/ioerror/tlsdate). They appear to have eschewed tlsdate's default approach of using the timestamp from the handshake in favor of using the `Date:` field, which tlsdate also supports. It would be interesting to see whether the randomization of TLS timestamps in modern implementations of TLS might mean that tlsdate's default mode is no longer useful. Either way, it's really cool to see this sort of functionality being included in ntpd by default!
[+] apenwarr|11 years ago|reply
openntpd has been nothing but trouble for me, but when I switched to djb clockspeed instead, it made things better. Here's a script that runs on GFiber devices, which uses tlsdate securely for the initial timewarp, and djb clockspeed thereafter. Since switching to this we have had extremely accurate timekeeping.

https://gfiber.googlesource.com/buildroot/+/master/fs/skelet...

[+] krakensden|11 years ago|reply
That is a really wonderful extension to ntpd. Simple, robust, with the server implementation for "free".
[+] VMG|11 years ago|reply
typo in submission title
[+] clarry|11 years ago|reply
typo in mail subject