centos7 apache 安装阿里云安全证书 ssl 测试成功

短命女 2021-09-29 10:42 369阅读 0赞

yum install mod\_ssl openssl 安装ssl

打开conf.d 下面的ssl.conf文件

# 添加 SSL 协议支持协议，去掉不安全的协议
    SSLProtocol all -SSLv2 -SSLv3
    # 修改加密套件如下
    SSLCipherSuite HIGH:!RC4:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!EXP:+MEDIUM
    SSLHonorCipherOrder on
    # 证书公钥配置
    SSLCertificateFile cert/public.pem
    # 证书私钥配置
    SSLCertificateKeyFile cert/214534250990130.key
    # 证书链配置，如果该属性开头有 '#'字符，请删除掉
    SSLCertificateChainFile cert/chain.pem

重启apache

如果访问的是apache那个页面，需要配置新的

DocumentRoot "/var/www/html/"  
ServerName xxx.xx.com:443

</VirtualHost>

多证书多域名

\# General setup for the virtual host, inherited from global configuration  
DocumentRoot "/var/www/html/xxx"  
ServerName xxx.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:!RC4:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!EXP:+MEDIUM

\# 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/httpd/cert/public.pem

\# 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/httpd/cert/xxxx.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/httpd/cert/chain.pem

\# 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.  
\#<Location />  
\#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\]+$/  
\#</Location>

\# 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  
<Files ~ "\\.(cgi|shtml|phtml|php3?)$">  
SSLOptions +StdEnvVars  
</Files>  
<Directory "/var/www/cgi-bin">  
SSLOptions +StdEnvVars  
</Directory>

\# 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"

</VirtualHost>

<VirtualHost _default_:443>
    
    # General setup for the virtual host, inherited from global configuration
    DocumentRoot "/var/www/html/xxxx"
    ServerName xxxi.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:!RC4:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!EXP:+MEDIUM
    
    #   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/httpd/certshop/public.pem
    
    #   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/httpd/certshop/xxx.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/httpd/certshop/chain.pem
    
    #   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.
    #<Location />
    #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]+$/
    #</Location>
    
    #   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
    <Files ~ "\.(cgi|shtml|phtml|php3?)$">
        SSLOptions +StdEnvVars
    </Files>
    <Directory "/var/www/cgi-bin">
        SSLOptions +StdEnvVars
    </Directory>
    
    #   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"
    
    </VirtualHost>

可能会出\_default\_ VirtualHost overlap on port 443, the first has precedence这问题

在httpd.conf

加上NameVirtualHost \*:443

简单理解 证书放在virtualhostl里面多个就配置多个

转载于:https://www.cnblogs.com/JANCHAN/p/8528302.html