Ubuntu-fr

flyght

accéder sur une page web en https avec apache

Bonjour,
J'ai un serveur Debian 6 avec apache et j'aimerais pouvoir accéder aux pages web de celui-ci via https au lieu de https.
J'ai suivi deja ce tuto, qui ne fonctionne pas           =>         http://doc.ubuntu-fr.org/tutoriel/secur … 2_avec_ssl
Pouvez vous m'aider ?

Voici ma configuration :

/etc/apache2/sites-available/default

<VirtualHost *:80>
#       Redirect / [url]https://X.X.fr/centreon/main.php[/url]
        Redirect / [url]https://X.X.fr/centreon/[/url]
        ServerName X.X.fr/

        ServerAdmin webmaster@localhost

        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        <Directory "/usr/lib/cgi-bin">
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all
        </Directory>

        ErrorLog ${APACHE_LOG_DIR}/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog ${APACHE_LOG_DIR}/access.log combined

#       <Location />
#               RewriteEngine on
#               RewriteCond %{HTTPS} off
#               RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R]
#       </Location>
</VirtualHost>

/etc/apache2/sites-available/default-ssl :

<IfModule mod_ssl.c>
<VirtualHost _default_:443>
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        <Directory "/usr/lib/cgi-bin">
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all
        </Directory>

        ErrorLog ${APACHE_LOG_DIR}/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined

        #   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.2-common/README.Debian.gz for more info.
        #   If both key and certificate are stored in the same file, only the
        #   SSLCertificateFile directive is needed.
       SSLCertificateFile    /usr/local/nagios/certificat/private/ca.crt
       SSLCertificateKeyFile /usr/local/nagios/certificat/private/ca.key
#       SSLCertificateFile /etc/apache2/ssl/apache.pem

        #   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/apache2/ssl.crt/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.
        #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
        #   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
#       <FilesMatch "\.(cgi|shtml|phtml|php)$">
#               SSLOptions +StdEnvVars
#       </FilesMatch>
#       <Directory /usr/lib/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-6]" \
#               nokeepalive ssl-unclean-shutdown \
#               downgrade-1.0 force-response-1.0
        # MSIE 7 and newer should be able to use keepalive
#       BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

</VirtualHost>
</IfModule>

Et /etc/apache2/ports.conf :

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz

NameVirtualHost *:80
Listen 80

<IfModule mod_ssl.c>
    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to <VirtualHost *:443>
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.
    NameVirtualHost *:443
    Listen 443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 443
</IfModule>

Donc bien sur tout ce qu'il y a en commenté n'est peut etre pas bon, car j'ai vu une quinzaine de configuration différente pour le https sur apache .... donc pas super
Donc avez vous une idée de comment configurer apache pour qu'il renvoi une page en https ???
Car moi aucune configuration ne fonctionne, je n'ai pas d'erreur quand je redémarre apache mais cela ne fonctionne pas quand meme ^^''

Merci

Dernière modification par flyght (Le 04/01/2013, à 11:13)

flyght

Re : accéder sur une page web en https avec apache

Déjà j'ai pensé à modifier ceci peut etre non ?
=> à la place de DocumentRoot /var/www il faudrai pas que je mette /usr/local/centreon/www
????

J'ai essayé cela ne fait rien mais peut etre qu'il y a une autre manip à faire en meme temps ?

tiramiseb

Re : accéder sur une page web en https avec apache

Pour desservir un site en HTTPS, les seules lignes indispensables sont les suivantes :

SSLEngine on
SSLCertificateFile    <chemin vers le certificat>
SSLCertificateKeyFile <chemin vers la clé>
SSLCACertificateFile  <chemin vers le certificat de l'autorité de certification>

J'ajoute également les lignes suivantes :

BrowserMatch "MSIE [2-6]" \
                nokeepalive ssl-unclean-shutdown \
                downgrade-1.0 force-response-1.0
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

Et je mets tout ça dans le Virtualhost suivant :

<VirtualHost *:443>

Ta configuration pour le SSL semble a priori correcte.

Tu écris : « aucune configuration ne fonctionne, je n'ai pas d'erreur quand je redémarre apache mais cela ne fonctionne pas quand meme »

Peux-tu préciser ce que tu effectues comme manipulation pour voir que ça ne marche pas, et comment tu vois que ça ne marche pas ?

Déjà j'ai pensé à modifier ceci peut etre non ?
=> à la place de DocumentRoot /var/www il faudrai pas que je mette /usr/local/centreon/www

Là ça n'a rien à voir avec le SSL, c'est à toi de configurer ton DocumentRoot selon tes besoins...

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

bruno

Re : accéder sur une page web en https avec apache

Le virtual host default-ssl est bien activé ? Au cas où :

sudo a2ensite default-ssl