CVE-2015-1799

mediumpriority · track · 17EPSS 0.009 · 60 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.90% (60th) EPSS
CVSS 4.3 · medium
Is it mine?
107 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · nvd · redhat_csaf

EPSS · scored 2026-10-27

The symmetric-key feature in the receive function in ntp_proto.c in ntpd in NTP 3.x and 4.x before 4.2.8p2 performs state-variable updates upon receiving certain invalid packets, which makes it easier for man-in-the-middle attackers to cause a denial of service (synchronization loss) by spoofing the source IP address of a peer.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. After installing the update, the ntpd daemon will restart automatically. Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:1459
  • Fixedntp-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Fixedsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

    https://access.redhat.com/errata/RHSA-2015:2231
  • Workaroundntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.src as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-5.el6.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-5.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-debuginfo-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-doc-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntp-perl-0:4.2.6p5-22.el7.noarch as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundntpdate-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

  • Workaroundsntp-0:4.2.6p5-22.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue.

02

cvss

Technical severity, 0–10. One row per scoring source.

4.3
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 3.7–4.3

v2.04.3mediumAV:A/AC:M/Au:N/C:N/I:P/A:Pprimary · NVD / NIST USexploitability 5.5 · impact 4.9
v2.03.7lowAV:A/AC:M/Au:N/C:N/I:P/A:P/E:Usecondary · CVSS-BT (t0sche)
v2.04.3mediumAV:N/AC:M/Au:N/C:N/I:N/A:Psecondary · Red Hat Product Security US
03

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-17USprimary
04

affected products (107)

Products and version ranges known to be affected.

showing 20 of 107
05

advisories (2)

Vendor and ecosystem advisories describing this.

  • RHSA-2015:1459Red Hat Security Advisory: ntp security, bug fix, and enhancement update2015-07-21csaf · redhat_csafUS

    Updated ntp packages that fix multiple security issues, several bugs, and add two enhancements are now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

  • RHSA-2015:2231Red Hat Security Advisory: ntp security, bug fix, and enhancement update2015-11-19csaf · redhat_csafUS

    Updated ntp packages that fix multiple security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

06

also known as (3)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

cnnvdenisa_euvdnvdredhat_csafNVDCVE.orgMITRE
published 2015-04-08modified 2026-06-17
09

references (51)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan