[Git][NTPsec/ntpsec][master] Remove "notrap" restrict option from config file example

Matt Selsky (@selsky) gitlab at mg.gitlab.com
Mon Apr 29 01:52:49 UTC 2024



Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
b5d1deca by Joachim Kross at 2024-04-28T22:58:18+02:00
Remove "notrap" restrict option from config file example

The "notrap" option to the restrict command is being ignored
since a while now, with a note to that effect being logged by
ntpd when it is found in the config file.

Remove the option from the config file example/default for SUSE.

- - - - -


1 changed file:

- packaging/SUSE/ntp.conf


Changes:

=====================================
packaging/SUSE/ntp.conf
=====================================
@@ -52,8 +52,8 @@
 # up blocking replies from your own upstream servers.
 
 # By default, exchange time with everybody, but don't allow configuration.
-restrict -4 default notrap nomodify nopeer noquery
-restrict -6 default notrap nomodify nopeer noquery
+restrict -4 default nomodify nopeer noquery
+restrict -6 default nomodify nopeer noquery
 
 # Local users may interrogate the ntp server more closely.
 restrict 127.0.0.1



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/b5d1deca3a68ba19f2dee12b10e469dc5ef8acdb

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/b5d1deca3a68ba19f2dee12b10e469dc5ef8acdb
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20240429/157eeaea/attachment.htm>


More information about the vc mailing list