What next?

Hal Murray halmurray at sonic.net
Sun Mar 17 21:00:13 UTC 2024


Is anybody thinking about what we should be doing?


Here is my list:

Port to Windows
  Does anybody know anything about Windows?
    Is there a decent POSIX environment?
    How well does waf work on Windows?
  We can get the magic code from ntp-classic.

I think we should split ntpd into several independant programs.
  More in another message.

I think we need a good SNTP client.  Something like the old ntpdate.
  I'm looking for a clean example.
  This would be a good opportunity to experiment with Go and/or Rust.

Getting off the ground.
  There is a chicken-egg problem with getting started when using NTS.  TLS 
needs the time to check certificates.  I think we can do something like skip 
the date part of certificate checking, then come back and see if the 
certificates pass the date-check after we have a candidate date.

Alternate port for use with NTS.
  There is a lot of blocking/filtering on port 123.  NTS-KE includes 
specifying the port to use.  We should be able to listen on another port too.  
I haven't looked carefully.  This feels like medium complexity.

-- 
These are my opinions.  I hate spam.





More information about the devel mailing list