RHSA-2020:2663

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the ntpd daemon will restart automatically.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.

1. Have enough trustworthy sources of time. 2. If you are serving time to a possibly hostile network, have your system get its time from other than unauthenticated IPv4 over the hostile network. 3. Use NTP packet authentication where appropriate. 4. Pay attention to error messages logged by ntpd. 5. Monitor your ntpd instances. If the pstats command of ntpq shows the value for "bogus origin" is increasing then that association is likely under attack. 6. If you must get unauthenticated time over IPv4 on a hostile network, Use restrict ... noserve to prevent this attack (note that this is a heavy-handed protection), which blocks time service to the specified network.

Use authentication with symmetric keys.