Shulou(Shulou.com)06/02 Report--

First of all, let's take a look at Ali Yun's official tutorial:

Document description:

1. The certificate file xxxxxx.pem contains two paragraphs. Please do not delete any of them.

two。 If it is the CSR created by the certificate system, it also includes: certificate private key file xxxxxxxx.key, certificate public key file public.pem, certificate chain file chain.pem.

(1) create the cert directory under the installation directory of Apache and copy all the downloaded files to the cert directory. If you created the CSR file when you applied for the certificate, put the corresponding private key file in the cert directory and name it xxxxxxxx.key

(2) Open the httpd.conf file in the conf directory under the apache installation directory, find the following and remove the "#":

# LoadModule ssl_module modules/mod_ssl.so (if you cannot find it, please confirm whether the openssl plug-in has been compiled) # Include conf/extra/httpd-ssl.conf

(3) Open the conf/extra/httpd-ssl.conf file under the apache installation directory (or conf.d/ssl.conf, depending on the operating system and installation method), and look for the following configuration statement in the configuration file:

# add the SSL protocol support protocol, remove the insecure protocol SSLProtocol all-SSLv2-SSLv3# to modify the cipher suite as follows: SSLCipherSuite HIGHV "RC4" RC4 "MD5"NullL"eNULL"Null"DH"EDH"EDH"exp"Medu MSSLHonorCipherOrder on# certificate public key configuration SSLCertificateFile cert/public.pem# certificate private key configuration SSLCertificateKeyFile cert/xxxxxxx.key# certificate chain configuration. If the attribute begins with the character" # ", delete the SSLCertificateKeyFile cert/xxxxxxx.key# certificate chain configuration.

(4) restart Apache.

(5) visit your site through https to test the installation and configuration of the site certificate. If you encounter a certificate mistrust problem, please check the help video.

However, this can only be used for reference. Under Ubuntu, I installed Apache with apt, but it has no httpd.conf, only an apache2.conf. Well, this file is similar to httpd.conf, and it is annotated like this:

# It is split into several files forming the configuration hierarchy outlined# below, all located in the / etc/apache2/ directory:## / etc/apache2/# |-- apache2.conf# | `--ports.conf# |-- mods-enabled# | |-- * .load# |`-- * .conf# |-- conf-enabled# | `--* .conf#`-- sites-enabled# `--* .conf #

This version of Apache distributes the configuration files into other small files, and the structure is the same as above. If you want, you can write a httpd.conf yourself and include it.

Let's focus on the configuration of https. The first step is to make sure that port 443 of your external environment is open.

The second step is to make sure you have ssl_module installed. Without apt-get install openssl, you may still need some dependencies, but they are all minor problems.

Then open ports.conf, the following sentences are indispensable:

Listen 443 Listen 443

Then open mods-available and find ssl.conf and ssl.load

Ssl.load looks like this:

# Depends: setenvif mime socache_shmcbLoadModule ssl_module / usr/lib/apache2/modules/mod_ssl.sossl.conf looks like this: # 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 builtin SSLRandomSeed startup file:/dev/urandom 512 SSLRandomSeed connect builtin SSLRandomSeed connect file:/dev/urandom 512 # SSL Global Context # All SSL configuration in this context applies both to # # the main server and all SSL-enabled virtual hosts. # Some MIME-types for downloading Certificates and CRLs # AddType application/x-x509-ca-cert .crt AddType application/x-pkcs7-crl .crl # Pass Phrase Dialog: # Configure the pass phrase gathering process. # The filtering dialog program (`builtin' is an internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog exec:/usr/share/apache2/ask-for-passphrase # Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds) # (The mechanism dbm has known memory leaks and should not be used). # SSLSessionCache dbm:$ {APACHE_RUN_DIR} / ssl_scache SSLSessionCache shmcb:$ {APACHE_RUN_DIR} / ssl_scache (512000) SSLSessionCacheTimeout 300 # Semaphore: # Configure the path to the mutual exclusion semaphore the # SSL engine uses internally for inter-process synchronization. # (Disabled by default, the global Mutex directive consolidates by default # this) # Mutex file:$ {APACHE_LOCK_DIR} / ssl_mutex ssl-cache # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate. See the # ciphers (1) man page from the openssl package for list of all available # options. # Enable only secure ciphers: medium # SSL server cipher order preference: # Use server priorities for cipher algorithm choice. SSLCipherSuite Higg, RC4, MD5, Null, EDH, exp. # Clients may prefer lower grade encryption. You should enable this # option if you want to enforce stronger encryption, and can afford # the CPU cost, and did not override SSLCipherSuite in a way that puts # insecure ciphers first. # Default: Off SSLHonorCipherOrder on # The protocols to enable. # Available values: all, SSLv3, TLSv1, TLSv1.1, TLSv1.2 # SSLv2 is no longer supported SSLProtocol all-SSLv2-SSLv3 # Allow insecure renegotiation with clients which do not yet support the # secure renegotiation protocol. Default: Off # SSLInsecureRenegotiation on # Whether to forbid non-SNI clients to access name based virtual hosts. # Default: Off # SSLStrictSNIVHostCheck On # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Then comes the configuration of the site, where the default default-ssl.conf is used:

ServerName # add your own site configuration # # Available loglevels: trace8,..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. # LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR} / error.log CustomLog ${APACHE_LOG_DIR} / access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf" # Include conf-available/serve-cgi-bin.conf # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # A self-signed (snakeoil) certificate can be created by installing # the ssl-cert package. See # / usr/share/doc/apache2/README.Debian.gz for more info. # If both key and certificate are stored in the same file, only the # SSLCertificateFile directive is needed. SSLCertificateFile / etc/apache2/cert/public.pem SSLCertificateKeyFile / etc/apache2/cert/xxxxxxx.key # Server CertificateChain: # 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/apache2/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) # 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 / etc/ssl/certs/ # SSLCACertificateFile / etc/apache2/ssl.crt/ca-bundle.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) # 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 / etc/apache2/ssl.crl/ # SSLCARevocationFile / etc/apache2/ssl.crl/ca-bundle.crl # 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 # 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 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-6]"\ # nokeepalive ssl-unclean-shutdown\ # downgrade-1.0 force-response-1.0 # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Did you find that the configuration items in the Aliyun tutorial are scattered into two configuration files?

Then use https to access it on the browser, which is successful. (linux can be tested using wget or curl)

The above is the whole content of this article, I hope it will be helpful to your study, and I also hope that you will support it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.