跳到主要內容

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
                2uca_1.ceruca_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

    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

# test.domain.com (2019/10/01)
 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






































































































留言

這個網誌中的熱門文章

魚那麼信任水,水卻把它煮了!

弘一大師說:“魚那麼信任水,水卻把它煮了;樹那麼信任風,風卻把它吹落;我那麼信任你,你卻把我傷害了。後來才發現,煮魚的不是水,而是火;吹落樹葉的不是風,而是季節;傷害我的也不是你,而是我的執念。任何關係走到最後,不過是相識一場。你若不傷,歲月無恙,其實真正能治癒你的不是時間,而是釋懷。”   這段話深刻地表達了信任和傷害之間的微妙關係,以及人們在感情中常常誤解的情境。弘一大師以魚信任水、樹信任風的比喻,巧妙地指出了信任的脆弱性。他指出,煮魚的是火而非水,吹落樹葉的是季節而非風,傷害人的是執念而非對方。  深刻的啟示: 文中的比喻教導人們要謹慎對待信任,不盲目將一切歸因於對方,而要意識到外在因素和自身的執念可能是傷害的源頭。這是一種深刻的啟示,提醒人們要以更審慎的態度面對人際關係 。  時間和釋懷的關係: 文中指出,真正能治癒的不是時間,而是釋懷。這強調了在感情受傷後,釋懷和理解是療癒的關鍵。時間只是一個流逝的工具,而真正的轉變需要內心的釋懷和接受。   相識一場的觀點: 最後的觀點指出,任何關係走到最後只是相識一場。這種看法強調了生命中的變動和無常,人們應該以寬容和理解的態度看待相處過程,並學會在過程中成長。   總的來說,這段話通過生動的比喻和深刻的洞察力,提供了對於信任、傷害和療癒的深刻思考,是一段引人深思的文字。

襄襄是一隻特別的虎皮鸚鵡

襄襄是一隻很特別的虎皮鸚鵡,她身上的羽衣非常獨特,總讓人忍不住多看幾眼。 她也很活潑好動,常常把她的週遭的物件,東抓西咬的翻弄著,但這也為我們家裡增添了不少歡樂氣氛。 媽媽很喜歡襄襄,她總是把襄襄帶在身邊,甚至幫她洗澡。襄襄也非常黏著媽媽,每次媽媽要出門,她都會飛到媽媽的頭髮上,一副要一起出門的樣子。 假日,全家要外出做半日旅遊,襄襄一發現,也總是纏著不放。似乎想要和我們出遊,最後,我們乾脆把她帶出門,一起去半日遊一番。襄襄在旅途中,也玩得很開心,一路上嘰嘰喳喳地叫個不停。 如今襄襄走了,回憶起往日,她曾陪伴著我們度過許許多多的快樂時光,真是令人懷念。她是我們家的一員,我們都很愛她。 2023年10月17日20:10我們失去了襄襄。 2023年10月18日03:55 初記。 2023年10月22日晚上21:00,我們決定把襄襄葬在後院空地。 大家幫襄襄用布包裹好,妹妹並寫給她一張紀念小張,我在布包外面寫了“襄襄”名字及安葬日期。然後由哥哥和妹妹帶去後院空地,挖掘安葬穴坑安葬,我也帶了三株開運竹(萬年青)種在穴位上,紀念襄襄。 2023年10月23日21:38補記。

搬家記

公司原在中和市,7月中要搬到台北市信義區,上班路程要加遠十公里,更辛苦了! 我很不喜歡搬家! 但搬家這件事,似乎和我結下不解之緣。 國中畢業後,我就開始搬家的旅程! 高中三年,搬六次家,平均每學期搬一次家! 大學四年,搬四次家,平均每學年搬一次家! 這十次的搬家很簡單,隨身家當除了棉被比較大件外,其餘的就是書籍,頂多請一個朋友幫忙,走一趟就完成了! 後來服兵役,我服預官役,短短一年十個月部隊移防超過十次,每個地方最短停留一周,最長九個月。其中有一半以上是部隊大移防,每次移防時,需要清點裝備,上車裝載,人員編組,然後在忙亂中移動到新位置,緊接著又開始卸裝備,清點裝備,安置定位,忙得天昏地暗。 最後一次移防,從基隆到左營集合,最後到金門,費時四天多。到金門時,天色已暗,大家還要摸黑集合到擎天廳,聽司令官訓話,回去休息時,已經超過晚上十時,又要忙著整理裝備,安排人員睡覺,等躺下來睡覺時已不知是凌晨幾點?還在睡夢中,突然聽到有人在呼叫,睜開眼一看,已經是早上七時,司令部的長官來叫我們去司令部掃地出公差。原來我們以後將是司令部專用的勤務連。 但嚴格來說,我在金門停留五個月,一直到退伍,算是服役當中最快樂的一段時光。 出社會工作一直到結婚前,總共四年,我換了二個工作,搬了二次家,還算穩定。 接著結婚生子到今天,前後十六年,我總共又搬了八次家,而居住新莊至今有八年。 回想起來,除了居住大安老家,共十六年的那段童年時光外,就以現在這個家最久了! 是呀! 這是我從公司搬遷這件事,讓我回想到一段人生旅程的點點滴滴! 公元2006年6月12日 12:36