The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
English Korean
To disable SSL version 2 and SSL version 3, which implies enabling everything except SSL version 2 and SSL version 3, in all VirtualHost sections, proceed as follows:
 
As `root`, open the `/etc/httpd/conf.d/ssl.conf` file and search for *all* instances of the [command]#SSLProtocol# directive. By default, the configuration file contains one section that looks as follows:
 
This step is particularly important if you have more than the one default VirtualHost section.
 
Note that any sessions will be interrupted.
 
Using an Existing Key and Certificate
 
indexterm:[Apache HTTP Server,SSL server,private key]indexterm:[Apache HTTP Server,SSL server,certificate] If you have a previously created key and certificate, you can configure the SSL server to use these files instead of generating new ones. There are only two situations where this is not possible:
 
*You are changing the IP address or domain name.*
 
Certificates are issued for a particular IP address and domain name pair. If one of these values changes, the certificate becomes invalid.
 
*You have a certificate from VeriSign, and you are changing the server software.*
 
VeriSign, a widely used certificate authority, issues certificates for a particular software product, IP address, and domain name. Changing the software product renders the certificate invalid.
 
In either of the above cases, you will need to obtain a new certificate. For more information on this topic, see xref:Web_Servers.adoc#s3-apache-mod_ssl-genkey[Generating a New Certificate Using OpenSSL].
 
If you want to use an existing key and certificate, move the relevant files to the `/etc/pki/tls/private/` and `/etc/pki/tls/certs/` directories respectively. You can do so by issuing the following commands as `root`:
 
Then add the following lines to the `/etc/httpd/conf.d/ssl.conf` configuration file:
 
To load the updated configuration, restart the `httpd` service as described in xref:Web_Servers.adoc#s3-apache-running-restarting[Restarting the Service].
 
Create a Certificate Signing Request(CSR). The Common Name field must be your server's hostname:
 
A message digest algorithm like SHA2 or stronger is recommended, but it's more important for the certificate than for the request. However your CA decides which message digest they use for the certificate.
 
Now give your CSR to your Certificate Authority(CA) so they can sign your key and give you a certificate:
 
You can also self-sign the CSR, but bear in mind the security issues that it poses and that browsers will warn users about this.
 
Once your CA has signed it, they will give you the certificate(`.crt` file). Now move the private key and the certificate to their respective directories:
 
The Certificate Signing Request(CSR) can be deleted as it becomes useless once you have obtained your certificate. Alternatively you can put it along your private key: