CentOS/CL7.1 CSF dhclient warning
Posted: 24 May 2015, 15:58
Our new CloudLinux 7.1 VPS has an extra warning when running Check Server Security...
Check for dhclient: dhclient appears to be running which suggests that the server is obtaining an IP address via DHCP. This can pose a security risk. You should configure static IP addresses for all ethernet controllers
Here is our /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet" # same as previous server (CL6)
# BOOTPROTO="dhcp" # removed 2015-05-24
# BOOTPROTO="none" # trialled 2015-05-24
BOOTPROTO="static" # added 2015-05-24
IPADDR=xx.xx.xx.xx # added 2015-05-24
# NETMASK=255.255.255.128 # not added from previous server (CL6)
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
NAME="eth0"
UUID="xx-xx-xx-xx-xx"
DEVICE="eth0" # same as previous server (CL6)
ONBOOT="yes" # same as previous server (CL6)
I can't find anything here or on the broader web about it.
Is the CSF warning misplaced now that BOOTPROTO is static?
It does sound rather non-committal compared to other CSF warnings.
Check for dhclient: dhclient appears to be running which suggests that the server is obtaining an IP address via DHCP. This can pose a security risk. You should configure static IP addresses for all ethernet controllers
Here is our /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet" # same as previous server (CL6)
# BOOTPROTO="dhcp" # removed 2015-05-24
# BOOTPROTO="none" # trialled 2015-05-24
BOOTPROTO="static" # added 2015-05-24
IPADDR=xx.xx.xx.xx # added 2015-05-24
# NETMASK=255.255.255.128 # not added from previous server (CL6)
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
NAME="eth0"
UUID="xx-xx-xx-xx-xx"
DEVICE="eth0" # same as previous server (CL6)
ONBOOT="yes" # same as previous server (CL6)
I can't find anything here or on the broader web about it.
Is the CSF warning misplaced now that BOOTPROTO is static?
It does sound rather non-committal compared to other CSF warnings.