...
Before You Begin
Ensure that System Requirements have been met prior to proceeding with the CentOS Configuration Guide.
...
1) Upgrade your current packages
Upgrade your current packages.
...
| Expand |
|---|
| title | Click here for the list of utilities... |
|---|
|
- curl
- openssl
- nmap
- bind-utils
- bind
- expect
- wget
- bzip2
|
| Code Block |
|---|
yum install curl openssl nmap bind-utils bind expect wget bzip2 |
...
| Expand |
|---|
Generate private key, CSR, and temporary key if one hasn't been provided.
| Code Block |
|---|
| openssl genrsa -out ca.key 1024
openssl req -new -key ca.key -out ca.csr
openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt |
Copy the files to the correct locations | Code Block |
|---|
| cp ca.crt /etc/pki/tls/certs
cp ca.key /etc/pki/tls/private/ca.key
cp ca.csr /etc/pki/tls/private/ca.csr |
| Note |
|---|
| Make sure that you copy the files and do not move them if SELinux is enabled (which it is by default) |
Edit the apache ssl config and put in the appropriate options: (shown using the vi editor, though you may use the editor of your choice)
| Code Block |
|---|
| vi /etc/httpd/conf.d/ssl.conf |
Find the lines that start with SSHCertificateFile and change them to be like: | Code Block |
|---|
| SSLCertificateFile /etc/pki/tls/certs/ca.crt
SSLCertificateKeyFile /etc/pki/tls/private/ca.key |
Then restart.
| Code Block |
|---|
| /etc/init.d/httpd restart |
Add 443 virtual hosts as needed in httpd.conf. |
...
| Code Block |
|---|
|
mysql -p -e "SET GLOBAL sql_mode='NO_ENGINE_SUBSTITUTION';SET SESSION sql_mode='NO_ENGINE_SUBSTITUTION';" |
Then enter the MySQL root password when prompted.
4) Optional configurations:
| Warning |
|---|
| title | READ THIS BEFORE YOU USE SELINUX |
|---|
|
SELinux is a very powerful method of securing the CentOS environment, but it is not "turn key" and requires expertise to configure it correctly. If you do not know how to configure SELinux, please do not use it. A badly configured SELinux install will not work well and result in frustration. If you have any questions or concerns about this - please contact 6connect Support at support@6connect.comsupport. |
| Note |
|---|
|
Please remember - if you change the IP address of the your server, then you will need to update SELinux functions accordingly |
Most CentOS install have SELinux enabled by default. One of its protections is to not allow httpd daemon to make network connections, we need to disable this for license checks.
To view the SELinux configuration for http:
| Code Block |
|---|
|
/usr/sbin/getsebool -a | grep httpd |
To turn protection off for the httpd daemon for creating network connections:
| Code Block |
|---|
|
/usr/sbin/setsebool -P httpd_can_network_connect 1 |
IPTables is enabled by default on CentOS. Add a new rule to allow 443 from anywhere. Make sure that this rule is in the chain BEFORE any blanket reject rule:
| Expand |
|---|
| title | If you are going to run iptables, click here |
|---|
|
To list all current IPTable rules:
| Code Block |
|---|
| /sbin/iptables RH-Firewall-1-INPUT -I 5 -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT |
| Note |
|---|
| | The -I 5 is what adds the rule to the 5th chain position. You might need to change this depending on existing rules. Look at what rules are there before running. |
To save the new config:
| Code Block |
|---|
| /etc/rc.d/init.d/iptables save |
OR (some versions of centOS have different iptables names, so the above won't work)
| Code Block |
|---|
| vi /etc/sysconfig/iptables |
With the file open for editing, add: | Code Block |
|---|
| -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT |
Once complete - restart the iptables service: | Code Block |
|---|
| /etc/init.d/iptables restart |
| Info |
|---|
| Customers can alter this post install to allow only their IP space, plus the 6connect ProVision management space. |
|
Radius (Optional)
...
| Code Block |
|---|
|
yum install libssh2-devel
pecl install -f ssh2
echo extension=ssh2.so > /etc/php.d/ssh2.ini |
5) Install
6connect ProVision Software:
1. Remove the current contents in the ProVision web folder (currently the www root) and after extract the archive contents (where 5.x.x is the version number for the build):
...