Apache Charge toujours les anciens certificats SSL (externe IP)

RedHat 6.2 Apache 2.2.15

J'ai installé un nouveau certificat SSL à votre serveur apache et mis à jour le fichier /etc/httpd/conf.d/ssl.conf, Y compris de nouvelles données:

#   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.  A new

# certificate can be generated using the genkey(1) command.

SSLCertificateFile /etc/httpd/ssl/2016/pathtocert.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.)

SSLCertificateKeyFile /etc/httpd/ssl/2016/pathtokey.key



#   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)

SSLCACertificateFile /etc/httpd/ssl/2016/bundle.crt

Après avoir redémarré httpd Et il utilise toujours un ancien certificat, qui expire quelques semaines. (J'ai aussi testé en exécutant un domaine à travers
https://www.digicert.com
)

J'ai confirmé qu'il utilise définitivement ce fichier. ssl.conf, Supprimer, puis le serveur ne démarre pas. Puis confirmé qu'il a définitivement chargé ces fichiers en modifiant le mauvais chemin, et le serveur n'a pas démissu de nouveau.

J'ai lancé ce qui suit depuis le terminal:

openssl s_client -connect domainhere.co.uk:443 -showcerts

Et il a montré les bons certificats (QuoVadis)

J'ai également essayé d'utiliser l'adresse IP du serveur et, encore une fois, il a renvoyé les bons certificats.

Ainsi, j'ai essayé d'utiliser une adresse IP externe, et c'était ici qu'il a renvoyé de vieux certificats. (TERENA), Donc c'est le problème.

Donc, je sais quel est le problème, mais je ne sais pas comment le réparer.

Dans mon fichier httpd.conf Il n'y a rien de SSL, Mais il y a des hôtes virtuels et NameVirtualHosts pour http Sur une adresse IP interne.

Toute la configuration SSL Situé dans le fichier ssl.conf, Où l'hôte virtuel utilise un nom de domaine au lieu d'une adresse IP:

Listen 443

(...)

<virtualhost mydomain.co.uk:443="">

#   SSL Engine Switch:

#   Enable/Disable SSL for this virtual host.

SSLEngine on



#   SSL Protocol support:

# List the enable protocol levels with which clients will be able to

# connect.  Disable SSLv2 access by default:

SSLProtocol all -SSLv2



#   SSL Cipher Suite:

# List the ciphers that the client is permitted to negotiate.

# See the mod_ssl documentation for a complete list.

SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW



#   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.  A new

# certificate can be generated using the genkey(1) command.

SSLCertificateFile /etc/httpd/ssl/2016/pathtocert.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.)

SSLCertificateKeyFile /etc/httpd/ssl/2016/pathto.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 convinience.

#SSLCertificateChainFile /etc/httpd/ssl/2016/bundle.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)

SSLCACertificateFile /etc/httpd/ssl/2016/bundle.crt



#   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></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} &gt;= 1 and %{TIME_WDAY} &lt;= 5 \

#            and %{TIME_HOUR} &gt;= 8 and %{TIME_HOUR} &lt;= 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

<files "\.(cgi|shtml|phtml|php3?)$"="" ~="">

        SSLOptions +StdEnvVars

</files>

<directory "="" cgi-bin"="" var="" www="">

        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.

SetEnvIf User-Agent ".*MSIE.*" \

                  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 logs/ssl_request_log \

                    "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"



</virtualhost>

Quelqu'un peut-il me conseiller que je dois modifier la configuration pour accéder à de nouveaux certificats via une adresse IP externe?

Remercier.