[email protected] said: > If this needs non trivial work on the server side, then you can say goodbye > to many servers in the pool...
There was no intention to require NTS. All the old stuff should continue to work as it currently does. If you are running ntpsec, it's pretty simple to add NTS support to an existing NTP server. First you have to get a certificate. If you are corporate, see your IT people. If you are home, try Let's Encrypt. Once you have the certificate, it's 3 new lines in the config file. You may need some firewall/NAT adjustments and/or to copy/link the cert file and private key to where ntpd can get it. The certificate requires that you have a DNS name for the IP Address for your server. Let's Encrypt requires that you have a real IP Address and probably matching forward/reverse DNS. On Fedora, it's: sudo dnf install certbot sudo certbot certonly --standalone Then every couple of months, they send you an email reminder and you need to run: sudo certbot renew -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
