It's now ok to use Google NTP servers (#5311)

1 files changed, 11 insertions, 13 deletions

diff --git a/DISTRO_PORTING b/DISTRO_PORTING
index 51a244389d..68107e46c9 100644
--- a/DISTRO_PORTING
+++ b/DISTRO_PORTING
@@ -25,21 +25,19 @@ HOWTO:
 
 NTP POOL:
 
-        By default, timesyncd uses the Google NTP servers
-        time[1-4].google.com. They serve time that is not standards
-        compliant, and can be up to .5s off. Google does not
-        officially support these servers for the broader
-        audience. Distributions and vendors really should not ship
-        OSes or devices with these NTP servers configured. Instead,
-        please register your own vendor pool at ntp.org and make it
-        the built-in default by passing --with-ntp-servers= to
-        configure. Registering vendor pools is free:
+        By default, timesyncd uses the Google Public NTP servers
+        time[1-4].google.com. They serve time that uses a leap second
+        smear, and can be up to .5s off from servers that use stepped
+        leap seconds.
 
-        http://www.pool.ntp.org/en/vendors.html
+        https://developers.google.com/time/smear
+
+        If you prefer to use leap second steps, please register your own
+        vendor pool at ntp.org and make it the built-in default by
+        passing --with-ntp-servers= to configure. Registering vendor
+        pools is free:
 
-        Again, if you ship your software or device with the default
-        NTP servers, then you will get served wrong time, and will
-        rely on services that might not be supported for long.
+        http://www.pool.ntp.org/en/vendors.html
 
 PAM:
         The default PAM config shipped by systemd is really bare bones.