[PATCH 4/4] added guidance for ntp encryption

Clifford Trueman ctrueman at ctrueman.csb
Mon Jul 16 19:26:14 UTC 2012


Signed-off-by: Clifford Trueman <ctrueman at redhat.com>
---
 RHEL6/input/services/ntp.xml |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/RHEL6/input/services/ntp.xml b/RHEL6/input/services/ntp.xml
index c1acd4a..f3ea935 100644
--- a/RHEL6/input/services/ntp.xml
+++ b/RHEL6/input/services/ntp.xml
@@ -1,6 +1,6 @@
 <Group id="ntp">
 <title>Network Time Protocol</title>
-<description>The Network Time Protocol is used to manage the system
+<description>check123 The Network Time Protocol is used to manage the system
 clock over a network. Computer clocks are not very accurate, so
 time will drift unpredictably on unmanaged systems. Central time
 protocols can be used both to ensure that time is consistent among
@@ -29,6 +29,9 @@ network to have a small number of machines operating as NTP
 servers, and the remainder obtaining time information from those
 internal servers.</description>
 
+
+
+
 <Group id="configuring_ntpd">
 <title>Configure an NTP Server</title>
 <description>The site's NTP server contacts a central NTP server,
@@ -66,6 +69,12 @@ providing time data from the local clock. However, it is a good idea to
 periodically synchronize the clock to some source of accurate time, even if it
 is not appropriate to do so automatically.</description>
 
+<Group id="ntpd_encryption">
+<title>NTP Encyrption</title>
+<description>Basically NTP uses encryption only for integrity checking and authentication (which effectively is integrity checking): symmetric keys (shared secrets) are used to prove authenticity of data received over the network key pairs are used where establishing shared secrets is difficult. The autokey mechanism uses key pairs. 
+</description>
+</Group>
+
 <Rule id="ntpd_specify_remote_server">
 <title>Specify a Remote NTP Server for Time Data</title>
 <description>A remote NTP Server for time synchronization should be specified.
-- 
1.7.1


--------------020109030703010904030300--


More information about the scap-security-guide mailing list