wamp开启SSL 使用HTTPS


首先进入wamp里面的Apache的bin目录下:

我的电脑是安装在D:\wampsoft\wamp\bin\apache\apache2.4.9\bin

在命令行执行:

set OPENSSL_CONF=../conf/openssl.cnf

set

接着生成私钥:

openssl genrsa > root.key   // 生成根密钥  
openssl genrsa > server.key  // 生成服务端密钥  
openssl genrsa > client.key  // 生成客户端密钥  

生成自签名的根证书

openssl req -x509 -new -key root.key > root.crt  
openssl req -new -key server.key -out server.csr  
openssl req -new -key client.key -out client.csr  

其中会要求我们输入一些信息如下:

Country Name (2 letter code) [AU]:CNISO国家代码(只支持两位字符)  
State or Province Name (full name) [Some-State]:ZJ所在省份  
Locality Name (eg, city) []:HZ所在城市  
Organization Name (eg, company):THS公司名称  
Organizational Unit Name (eg, section) []:THS组织名称  
Common Name (eg, YOUR name) []:localhost(申请证书的域名或IP地址)  
Email Address []:laoniangke@xxx.com管理员邮箱  
   
Please enter the following 'extra' attributes  
to be sent with your certificate request  
A challenge password []:交换密钥  可以为空
An optional company name []:  可以为空

接着输入命令:

md demoCA  

md demoCA\newcerts  

md demoCA\private  

cd. > demoCA\index.txt  

echo 01 > demoCA\serial  

echo 01 > demoCA\crlnumber  

openssl genrsa -out demoCA/private/cakey.pem 2048  

openssl req -out demoCA/cacert.pem -x509 -new -key demoCA/private/cakey.pem  

然后修改配置文件:D:\wampsoft\wamp\bin\apache\apache2.4.9\conf\openssl.cnf

# ../conf/openssl.cnf  
dir        = ./demoCA # Where everything is kept  
certs        = $dir/certs        # Where the issued certs are kept  
crl_dir        = $dir/crl        # Where the issued crl are kept  
database    = $dir/index.txt    # database index file.  
new_certs_dir    = $dir/newcerts        # default place for new certs.   
certificate    = $dir/cacert.pem     # The CA certificate  
serial        = $dir/serial         # The current serial number  
crlnumber    = $dir/crlnumber    # the current crl number  
crl        = $dir/crl.pem         # The current CRL  
private_key    = $dir/private/cakey.pem# The private key  
RANDFILE    = $dir/private/.rand    # private random number file  

默认好像就是这样,不用修改。

使用根证书为服务端及客户端签名,输入命令如下:

openssl ca -in server.csr -cert root.crt -keyfile root.key -out server.crt  
openssl ca -in client.csr -cert root.crt -keyfile root.key -out client.crt  

将客户端证书转成pfx格式,并在浏览器上导入该证书 转换命令如下:

openssl pkcs12 -export -clcerts -in client.crt -inkey client.key -out client.pfx  

配置D:\wampsoft\wamp\bin\apache\apache2.4.9\conf\http.conf

去掉下面的注释:

LoadModule socache_shmcb_module modules/mod_socache_shmcb.so 
LoadModule sslmodule modules/modssl.so  
Include conf/extra/httpd-ssl.conf  

最后修改配置文件D:\wampsoft\wamp\bin\apache\apache2.4.9\conf\extra\http-ssl.conf

Listen 443

SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

SSLPassPhraseDialog  builtin



#   General setup for the virtual host
DocumentRoot "D:/www/qiurank/"
ServerName www.example.com:443
ServerAdmin admin@example.com
ErrorLog "D:/wampsoft/wamp/logs/error.log"
TransferLog "D:/wampsoft/wamp/logs/access.log"

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine 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.  Keep
#   in mind that if you have both an RSA and a DSA certificate you
#   can configure both in parallel (to also allow the use of DSA
#   ciphers, etc.)
#   Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
#   require an ECC certificate which can also be configured in
#   parallel.
SSLCertificateFile "D:/wampsoft/wamp/bin/apache/apache2.4.9/bin/server.crt"
#SSLCertificateFile "c:/Apache24/conf/server-dsa.crt"
#SSLCertificateFile "c:/Apache24/conf/server-ecc.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.)
#   ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile "D:/wampsoft/wamp/bin/apache/apache2.4.9/bin/server.key"
#SSLCertificateKeyFile "c:/Apache24/conf/server-dsa.key"
#SSLCertificateKeyFile "c:/Apache24/conf/server-ecc.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 convenience.
#SSLCertificateChainFile "c:/Apache24/conf/server-ca.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)
#   Note: Inside SSLCACertificatePath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCACertificatePath "c:/Apache24/conf/ssl.crt"
SSLCACertificateFile "D:/wampsoft/wamp/bin/apache/apache2.4.9/bin/root.crt"

#   Certificate Revocation Lists (CRL):
#   Set the CA revocation path where to find CA CRLs for client
#   authentication or alternatively one huge file containing all
#   of them (file must be PEM encoded).
#   The CRL checking mode needs to be configured explicitly
#   through SSLCARevocationCheck (defaults to "none" otherwise).
#   Note: Inside SSLCARevocationPath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCARevocationPath "c:/Apache24/conf/ssl.crl"
#SSLCARevocationFile "c:/Apache24/conf/ssl.crl/ca-bundle.crl"
#SSLCARevocationCheck chain

#   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

#   TLS-SRP mutual authentication:
#   Enable TLS-SRP and set the path to the OpenSSL SRP verifier
#   file (containing login information for SRP user accounts). 
#   Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for
#   detailed instructions on creating this file. Example:
#   "openssl srp -srpvfile c:/Apache24/conf/passwd.srpv -add username"
#SSLSRPVerifierFile "c:/Apache24/conf/passwd.srpv"

#   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 sent or allowed to be 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 "D:/wampsoft/wamp/logs/ssl_request.log" \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

                                  

Leave a comment