CentOS 7 安裝 Apache 2.4 / 設定http https reverse proxy

CentOS 7 安裝 Apache 2.4 / 設定http,https reverse proxy

架構：

1.Apache的安裝與設定

指令：sudo yum install httpd -y

     安裝apache

指令：sudo systemctl enable httpd

               設定 Apache 服務隨系統一起啟動

指令：sudo systemctl start httpd

   啟動 apache

指令：sudo systemctl restart httpd

            重新啟動 apache

指令：sudo httpd -v

   檢查apache版本

預設支援tcp6，若只要支援tcp

修改/etc/httpd/httpd.conf

Listen 0.0.0.0:80

再重啟httpd

2.系統安全與防火牆

CentOS 7 的 SELinux 及 Firewalld 防火牆

都是安全相關的套件,  CentOS 預設開啟, 如果在測試的機器上, 將它們關閉對除錯方便不少。

關閉 SELinux:

開啟檔案 /etc/selinux/config:

找到以下一行:
SELINUX=enforce
改成:
SELINUX=disabled
另外將 “SELINUXTYPE=targeted” 加上註釋, 改成這樣:
# SELINUXTYPE=targeted

儲存後離開編輯器, 需要重新開機設定才會生效。
要檢查 SELinux 的狀態, 執行 sestatus 指令便可以看到:

關閉 Firewalld 防火牆指令:

# systemctl stop firewalld.service

設定下次開機不會啟動 Firewalld 防火牆

# systemctl disable firewalld.service

3.安裝SSL
yum install mod_ssl openssl

4.匯入與配置SSL憑證

a.上傳憑證testssl.pfx 到 /root

b.轉換憑證格式：

(1) .pfx → .crt

[root@proxy-server ~]# openssl pkcs12 -in testssl.pfx -clcerts -nokeys -out testssl.crt

Enter Import Password:

MAC verified OK

複製到 /etc/pki/tls/certs/testssl.crt

(2) .pfx → .key

[root@proxy-server ~]# openssl pkcs12 -in testssl.pfx -nocerts -nodes -out testssl.key

Enter Import Password:

MAC verified OK

複製到/etc/pki/tls/private/testssl.key



            (3)合併中繼憑證：合併2張中繼憑證 .cer → .cer

  將2張uca_1.cer與uca_2.cer合併成一張中繼憑證uca.crt後上傳

          使用筆記本先將uca_2.cer內容複製貼上，接著再將uca_1.cer內容複製貼上，

然後存成 uca.crt ，上傳到/etc/pki/tls/certs/uca.crt

(4).憑證清單與位置

/etc/pki/tls/private   1張憑證 testssl.key

/etc/pki/tls/certs/     2張憑證 testssl.crt uca.crt

5.配置SSL

vi /etc/httpd/conf.d/ssl.conf

#

# When we also provide SSL we have to listen to the

# the HTTPS port in addition.

#

Listen 0.0.0.0:443 https

##

## SSL Global Context

##

## All SSL configuration in this context applies both to

## the main server and all SSL-enabled virtual hosts.

##

#   Pass Phrase Dialog:

#   Configure the pass phrase gathering process.

#   The filtering dialog program (`builtin' is a internal

#   terminal dialog) has to provide the pass phrase on stdout.

SSLPassPhraseDialog exec:/usr/libexec/httpd-ssl-pass-dialog

#   Inter-Process Session Cache:

#   Configure the SSL Session Cache: First the mechanism

#   to use and second the expiring timeout (in seconds).

SSLSessionCache         shmcb:/run/httpd/sslcache(512000)

SSLSessionCacheTimeout 300

#   Pseudo Random Number Generator (PRNG):

#   Configure one or more sources to seed the PRNG of the

#   SSL library. The seed data should be of good random quality.

#   WARNING! On some platforms /dev/random blocks if not enough entropy

#   is available. This means you then cannot use the /dev/random device

#   because it would lead to very long connection times (as long as

#   it requires to make more entropy available). But usually those

#   platforms additionally provide a /dev/urandom device which doesn't

#   block. So, if available, use this one instead. Read the mod_ssl User

#   Manual for more details.

SSLRandomSeed startup file:/dev/urandom 256

SSLRandomSeed connect builtin

#SSLRandomSeed startup file:/dev/random 512

#SSLRandomSeed connect file:/dev/random 512

#SSLRandomSeed connect file:/dev/urandom 512

#

# Use "SSLCryptoDevice" to enable any supported hardware

# accelerators. Use "openssl engine -v" to list supported

# engine names. NOTE: If you enable an accelerator and the

# server does not start, consult the error logs and ensure

# your accelerator is functioning properly.

#

SSLCryptoDevice builtin

#SSLCryptoDevice ubsec

##

## SSL Virtual Host Context

##

# General setup for the virtual host, inherited from global configuration

#DocumentRoot "/var/www/html"

#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel

# is not inherited from httpd.conf.

ErrorLog logs/ssl_error_log

TransferLog logs/ssl_access_log

LogLevel warn

#   SSL Engine Switch:

#   Enable/Disable SSL for this virtual host.

SSLEngine on

#   SSL Protocol support:

# List the enable protocol levels with which clients will be able to

# connect. Disable SSLv2 access by default:

SSLProtocol all -SSLv2 -SSLv3

#   SSL Cipher Suite:

#   List the ciphers that the client is permitted to negotiate.

#   See the mod_ssl documentation for a complete list.

SSLCipherSuite HIGH:3DES:!aNULL:!MD5:!SEED:!IDEA

#   Speed-optimized SSL Cipher configuration:

#   If speed is your main concern (on busy HTTPS servers e.g.),

#   you might want to force clients to specific, performance

#   optimized ciphers. In this case, prepend those ciphers

#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.

#   Caveat: by giving precedence to RC4-SHA and AES128-SHA

#   (as in the example below), most connections will no longer

#   have perfect forward secrecy - if the server's key is

#   compromised, captures of past or future traffic must be

#   considered compromised, too.

#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5

#SSLHonorCipherOrder on

#   Server Certificate:

# Point SSLCertificateFile at a PEM encoded certificate. If

# the certificate is encrypted, then you will be prompted for a

# pass phrase. Note that a kill -HUP will prompt again. A new

# certificate can be generated using the genkey(1) command.

# SSLCertificateFile /etc/pki/tls/certs/localhost.crt

#       --------------------- TESTSSL : 2張 crt--------------------------

SSLCertificateFile /etc/pki/tls/certs/testssl.crt

SSLCertificateChainFile /etc/pki/tls/certs/uca.crt

#     -------------------------------------------------------------------

#   Server Private Key:

#   If the key is not combined with the certificate, use this

#   directive to point at the key file. Keep in mind that if

#   you've both a RSA and a DSA private key you can configure

#   both in parallel (to also allow the use of DSA ciphers, etc.)

#       SSLCertificateKeyFile /etc/pki/tls/private/localhost.key

#      --------------------- TESTSSL : 1張 key--------------------------

SSLCertificateKeyFile /etc/pki/tls/private/testssl.key

#     ------------------------------------------------------------------

#   Server Certificate Chain:

#   Point SSLCertificateChainFile at a file containing the

#   concatenation of PEM encoded CA certificates which form the

#   certificate chain for the server certificate. Alternatively

#   the referenced file can be the same as SSLCertificateFile

#   when the CA certificates are directly appended to the server

#   certificate for convinience.

#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt

#   Certificate Authority (CA):

#   Set the CA certificate verification path where to find CA

#   certificates for client authentication or alternatively one

#   huge file containing all of them (file must be PEM encoded)

#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   Client Authentication (Type):

#   Client certificate verification type and depth. Types are

#   none, optional, require and optional_no_ca. Depth is a

#   number which specifies how deeply to verify the certificate

#   issuer chain before deciding the certificate is not valid.

#SSLVerifyClient require

#SSLVerifyDepth 10

#   Access Control:

#   With SSLRequire you can do per-directory access control based

#   on arbitrary complex boolean expressions containing server

#   variable checks and other lookup directives. The syntax is a

#   mixture between C and Perl. See the mod_ssl documentation

#   for more details.

#

#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \

#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \

#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \

#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \

#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \

#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/

#

# SSL Engine Options:

# Set various options for the SSL engine.

# o FakeBasicAuth:

# Translate the client X.509 into a Basic Authorisation. This means that

# the standard Auth/DBMAuth methods can be used for access control. The

# user name is the `one line' version of the client's X.509 certificate.

# Note that no password is obtained from the user. Every entry in the user

# file needs this password: `xxj31ZMTZzkVA'.

# o ExportCertData:

# This exports two additional environment variables: SSL_CLIENT_CERT and

# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the

# server (always existing) and the client (only existing when client

# authentication is used). This can be used to import the certificates

# into CGI scripts.

# o StdEnvVars:

# This exports the standard SSL/TLS related `SSL_*' environment variables.

# Per default this exportation is switched off for performance reasons,

# because the extraction step is an expensive operation and is usually

# useless for serving static content. So one usually enables the

# exportation for CGI and SSI requests only.

# o StrictRequire:

# This denies access when "SSLRequireSSL" or "SSLRequire" applied even

# under a "Satisfy any" situation, i.e. when it applies access is denied

# and no other module can change it.

# o OptRenegotiate:

# This enables optimized SSL connection renegotiation handling when SSL

# directives are used in per-directory context.

#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

SSLOptions +StdEnvVars

# SSL Protocol Adjustments:

# The safe and default but still SSL/TLS standard compliant shutdown

# approach is that mod_ssl sends the close notify alert but doesn't wait for

# the close notify alert from client. When you need a different shutdown

# approach you can use one of the following variables:

# o ssl-unclean-shutdown:

# This forces an unclean shutdown when the connection is closed, i.e. no

# SSL close notify alert is send or allowed to received. This violates

# the SSL/TLS standard but is needed for some brain-dead browsers. Use

# this when you receive I/O errors because of the standard approach where

# mod_ssl sends the close notify alert.

# o ssl-accurate-shutdown:

# This forces an accurate shutdown when the connection is closed, i.e. a

# SSL close notify alert is send and mod_ssl waits for the close notify

# alert of the client. This is 100% SSL/TLS standard compliant, but in

# practice often causes hanging connections with brain-dead browsers. Use

# this only for browsers where you know that their SSL implementation

# works correctly.

# Notice: Most problems of broken clients are also related to the HTTP

# keep-alive facility, so you usually additionally want to disable

# keep-alive for those clients, too. Use variable "nokeepalive" for this.

# Similarly, one has to force some clients to use HTTP/1.0 to workaround

# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and

# "force-response-1.0" for this.

BrowserMatch "MSIE [2-5]" \

nokeepalive ssl-unclean-shutdown \

downgrade-1.0 force-response-1.0

# Per-Server Logging:

# The home of a custom SSL log file. Use this when you want a

# compact non-error SSL logfile on a virtual host basis.

CustomLog logs/ssl_request_log \

"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

6.設定reverse proxy

https設定

vi /etc/httpd/conf.d/ 01-ssl-web01-web02.conf

NameVirtualHost proxy-server:443

# test.domain.com (2019/10/01)

SSLEngine on

SSLProtocol all -SSLv2 -SSLv3 -TLSv1

SSLHonorCipherOrder on

SSLCipherSuite kEECDH:+kEECDH+SHA:kEDH:+kEDH+SHA:+kEDH+CAMELLIA:kECDH:+kECDH+SHA:kRSA:+kRSA+SHA:+kRSA+CAMELLIA:!aNULL:!eNULL:!SSLv2:!SSLv3:!TLSv1:!RC4:!DES:!EXP:!SEED:!IDEA:!3DES

ErrorLog logs/ssl_error_log

TransferLog logs/ssl_access_log

LogLevel warn

CustomLog logs/ssl_request_log \

"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

SSLCertificateKeyFile /etc/pki/tls/private/cnyesssl.key

SSLCertificateFile /etc/pki/tls/certs/cnyesssl.crt

SSLCertificateChainFile /etc/pki/tls/certs/uca.crt

ServerName test.domain.com

DocumentRoot "/"

ProxyPass "/" "balancer://testdomain/"

ProxyPassReverse "/" "balancer:// testdomain /"

BalancerMember http://10.65.1.1:80 route=node1 loadfactor=1

BalancerMember http://10.65.1.2:80 route=node2 loadfactor=1

ProxySet lbmethod=byrequests

Order deny,allow

Allow from all

ProxyRequests Off

ProxyPreserveHost On

SetEnv force-proxy-request-1.0 1

SetEnv proxy-initial-not-pooled

SetEnv proxy-nokeepalive 1

http設定

vi /etc/httpd/conf.d/01-http-web01-web02.conf

NameVirtualHost proxy-server:80