Les tutos de Pisto

Outils pour utilisateurs

Outils du site

Vous êtes ici : start » linux » installation » openssl
Piste :
linux:installation:openssl

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision		Révision précédente
linux:installation:openssl [2022/09/03 14:50] – [Creating an Apache Configuration Snippet with Strong Encryption Settings] tutospistolinux:installation:openssl [2022/09/03 14:58] (Version actuelle) – [Step 5 — Testing Encryption] tutospisto
Ligne 84: Ligne 84:
  
 **/etc/apache2/sites-available/default-ssl.conf** **/etc/apache2/sites-available/default-ssl.conf**
-<code apache>+<code apache[enable_line_numbers=1]>
 <IfModule mod_ssl.c> <IfModule mod_ssl.c>
         <VirtualHost _default_:443>         <VirtualHost _default_:443>
Ligne 109: Ligne 109:
 </IfModule> </IfModule>
 </code> </code>
 +
 +We will be making some minor adjustments to the file. We will set the normal things we’d want to adjust in a Virtual Host file (ServerAdmin email address, ServerName, etc.), and adjust the SSL directives to point to our certificate and key files. Again, if you’re using a different document root, be sure to update the DocumentRoot directive.
 +
 +After making these changes, your server block should look similar to this:
 +
 +/etc/apache2/sites-available/default-ssl.conf
 +
 +<code apache[enable_line_numbers=1]>
 +<IfModule mod_ssl.c>
 +        <VirtualHost _default_:443>
 +                ServerAdmin your_email@example.com
 +                ServerName server_domain_or_IP
 + 
 +                DocumentRoot /var/www/html
 + 
 +                ErrorLog ${APACHE_LOG_DIR}/error.log
 +                CustomLog ${APACHE_LOG_DIR}/access.log combined
 + 
 +                SSLEngine on
 + 
 +                SSLCertificateFile      /etc/ssl/certs/apache-selfsigned.crt
 +                SSLCertificateKeyFile /etc/ssl/private/apache-selfsigned.key
 + 
 +                <FilesMatch "\.(cgi|shtml|phtml|php)$">
 +                                SSLOptions +StdEnvVars
 +                </FilesMatch>
 +                <Directory /usr/lib/cgi-bin>
 +                                SSLOptions +StdEnvVars
 +                </Directory>
 + 
 +        </VirtualHost>
 +</IfModule>
 +</code>
 +
 +Save and close the file when you are finished.
 +
 +=== (Recommended) Modifying the HTTP Host File to Redirect to HTTPS ===
 +As it stands now, the server will provide both unencrypted HTTP and encrypted HTTPS traffic. For better security, it is recommended in most cases to redirect HTTP to HTTPS automatically. If you do not want or need this functionality, you can safely skip this section.
 +
 +To adjust the unencrypted Virtual Host file to redirect all traffic to be SSL encrypted, open the /etc/apache2/sites-available/000-default.conf file:
 +<code bash>sudo nano /etc/apache2/sites-available/000-default.conf</code>
 +
 +Inside, within the VirtualHost configuration blocks, add a Redirect directive, pointing all traffic to the SSL version of the site:
 +
 +**/etc/apache2/sites-available/000-default.conf**
 +
 +<code bash><VirtualHost *:80>
 +        . . .
 + 
 +        Redirect "/" "https://your_domain_or_IP/"
 + 
 +        . . .
 +</VirtualHost></code>
 +
 +
 +
 +Save and close the file when you are finished.
 +
 +That’s all of the configuration changes you need to make to Apache. Next, we will discuss how to update firewall rules with ufw to allow encrypted HTTPS traffic to your server.
 +===== Step 3 — Adjusting the Firewall =====
 +
 +Je n’ai pas réalisé cette étape.
 +
 +===== Step 4 — Enabling the Changes in Apache =====
 +
 +Now that we’ve made our changes and adjusted our firewall, we can enable the SSL and headers modules in Apache, enable our SSL-ready Virtual Host, and then restart Apache to put these changes into effect.
 +
 +Enable mod_ssl, the Apache SSL module, and mod_headers, which is needed by some of the settings in our SSL snippet, with the a2enmod command:
 +
 +<code bash>
 +sudo a2enmod ssl
 +sudo a2enmod headers
 +sudo a2ensite default-ssl
 +sudo a2enconf ssl-params
 +</code>
 +
 +
 +
 +At this point, the site and the necessary modules are enabled. We should check to make sure that there are no syntax errors in our files. Do this by typing:
 +<code bash>sudo apache2ctl configtest</code>
 +
 +
 +
 +If everything is successful, you will get a result that looks like this:
 +
 +<code bash>Output
 +Syntax OK</code>
 +
 +
 +As long as your output has Syntax OK in it, then your configuration file has no syntax errors and you can safely restart Apache to implement the changes:
 +
 +<code bash>sudo systemctl restart apache2</code>
 +
 +
 +With that, your self-signed SSL certificate is all set. You can now test that your server is correctly encrypting its traffic.
 +
 +
 +===== Step 5 — Testing Encryption =====
 +
 +
 +You’re now ready to test your SSL server.
 +
 +Open your web browser and type <code bash>https://</code> followed by your server’s domain name or IP into the address bar:
 +
 +<code bash>https://server_domain_or_IP</code>
 +
 +Because the certificate you created isn’t signed by one of your browser’s trusted certificate authorities, you will likely see a scary looking warning like the one below:Apache self-signed cert warningThis is expected and normal. We are only interested in the encryption aspect of our certificate, not the third party validation of our host’s authenticity. Click ADVANCED and then the link provided to proceed to your host anyways:Apache self-signed override
 +
 +You should be taken to your site. If you look in the browser address bar, you will see a lock with an « x » over it or another similar “not secure” notice. In this case, this just means that the certificate cannot be validated. It is still encrypting your connection.
 +
 +If you configured Apache to redirect HTTP to HTTPS, you can also check whether the redirect functions correctly:
 +
 +<code bash>http://server_domain_or_IP</code>
 +
 +If this results in the same icon, this means that your redirect worked correctly. However, the redirect you created earlier is only a temporary redirect. If you’d like to make the redirection to HTTPS permanent, continue on to the final step.
 +===== Step 6 — Changing to a Permanent Redirect =====
 +
 +
 +If your redirect worked correctly and you are sure you want to allow only encrypted traffic, you should modify the unencrypted Apache Virtual Host again to make the redirect permanent.
 +
 +Open your server block configuration file again:
 +<code bash>sudo nano /etc/apache2/sites-available/000-default.conf</code>
 +
 +Find the Redirect line we added earlier. Add permanent to that line, which changes the redirect from a 302 temporary redirect to a 301 permanent redirect:
 +
 +**/etc/apache2/sites-available/000-default.conf**
 +<code bash><VirtualHost *:80>
 +        . . .
 + 
 +        Redirect permanent "/" "https://your_domain_or_IP/"
 + 
 +        . . .
 +</VirtualHost></code>
 +
 +Save and close the file.
 +
 +Check your configuration for syntax errors:
 +<code bash>sudo apache2ctl configtest</code>
 +
 +If this command doesn’t report any syntax errors, restart Apache:
 +<code bash>sudo systemctl restart apache2</code>
 +
 +This will make the redirect permanent, and your site will only serve traffic over HTTPS.
  
linux/installation/openssl.1662216645.txt.gz · Dernière modification : 2022/09/03 14:50 de tutospisto

Outils de la page

Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki Nom de domaine