M e r i d i a n I I U s e r M a n u a l
62
C H A P T E R F I V E
63
M e r i d i a n I I U s e r M a n u a l
S E C U R I T Y
After making and saving your changes, you must copy the edited file to the non-volatile FLASH area
and reboot the unit:
cp -p /etc/httpd/httpd.conf /boot/etc/httpd
reboot
Restrict Query Access - NTP
The Network Time Protocol (NTP) implementation in Meridian II is built from the reference distribu-
tion from:
By factory default, remote control and query of the NTP daemon
ntpd
is disabled. Query-only
operation is supported only from processes running on Meridian II itself, i.e. from the
localhost
. This
restricts access to
ntpd
from remote hosts using either of the two NTP companion utilities
ntpq
and
ntpdc
.
Control via these two utilities is disabled in the
/etc/ntp.conf
file in two ways. First, MD5 authentica-
tion keys are not defined for control operation via a
requestkey
or
controlkey
declaration. Second,
this default address restriction line is present in the file:
restrict default nomodify noquery nopeer
restrict 127.0.0.1 nomodify
restrict 0::1 nomodify
The first line eliminates control and query access from ALL hosts. The second and third lines disable
the localhost from making any modifications to the
ntpd
daemon, but query access is not affected
by this restriction. These lines must not be removed, as they are necessary for various monitoring
processes running on Meridian II to function properly.
Knowledgable NTP users who would like to customize the security aspects of the configuration of the
NTP daemon in Meridian II should edit the
/etc/ntp.conf
file directly and then copy it to the
/boot/etc
directory. Be sure to retain the ownership and permissions of the original file by using
cp –p
when
performing the copy.
CAUTION
If you are planning to make changes to the
/etc/ntp.conf
file, you must NOT restrict query access from
the local host to the NTP daemon. Various system monitoring processes running on the system require this
access.
An example follows which shows how to allow query access from a specific remote host with IP
address 192.168.1.10 while also allowing processes running on Meridian II to have query access as
well:
Summary of Contents for Meridian II
Page 2: ......
Page 20: ...M e r i d i a n I I U s e r M a n u a l This page intentionally left blank...
Page 139: ...119 M e r i d i a n I I U s e r M a n u a l R E A R P A N E L I O...
Page 216: ...M e r i d i a n I I U s e r M a n u a l 196 A P P E N D I X J...
Page 235: ...215 M e r i d i a n I I U s e r M a n u a l S P E C I F I C AT I O N S...
Page 236: ...M e r i d i a n I I U s e r M a n u a l 216 A P P E N D I X K...
Page 239: ......
