Je viens de suivre ce topic "AIDE pour OpenSSL avec WampServer 2.0i": [forum.wampserver.com]. Tout semble s'être bien passé, par contre quand je redémarre Wamp, il ne se lance plus. J'ai aucune erreur dans le fichier error.log d'Apache, également je n'ai aucun fichier de créé dans le dossier: C:\wamp\bin\apache\apache2.2.22\conf\ssl\logs.
Les derniers logs que j'obtiens dans apache_error.log sont:
[Thu Apr 04 15:11:28 2013] [notice] Parent: Received shutdown signal -- Shutting down the server. [Thu Apr 04 15:11:28 2013] [notice] Child 10028: Exit event signaled. Child process is ending. [Thu Apr 04 15:11:29 2013] [notice] Child 10028: Released the start mutex [Thu Apr 04 15:11:30 2013] [notice] Child 10028: All worker threads have exited. [Thu Apr 04 15:11:30 2013] [notice] Child 10028: Child process is exiting [Thu Apr 04 15:11:30 2013] [notice] Parent: Child process exited successfully.
Depuis plus rien, impossible de déboguer seul, pourriez-vous m'aider?
Merci à tous.
Edit:
Wamp redémarre quand je recommente la ligne: Include conf/extra/httpd-ssl.conf J'ai testé avec le fichier initial présent dans Wamp (sans les modifications du topic), idem ça plante.
Modifie 3 fois. Derniere modification le 04/04/2013 à 16:05 par sGendt.
Le fichier original ne fonctionne pas, et c'est normal Pourriez-vous indiquer les erreurs obtenus avec votre fichier httpd-ssl.conf ainsi que le contenu de votre fichier httpd-ssl.conf ? Merci
Concernant les erreurs, j'en ai aucune dans les fichiers log, uniquement wamp ne démarre pas, très étrange Apache ne trace plus rien, php et mysql idem et pour le dossier logs créé dans le topic absolument rien ne s'y trouve.
Concernant le contenu du fichier httpd-ssl.conf qui se trouve C:\wamp\bin\apache\apache2.2.22\conf\extra sur mon ordinateur, le voici (Tous les modifications que j'avais effectué suite au topic sont commentées, elles se trouvent en dessous des originales):
# # This is the Apache server configuration file providing SSL support. # It contains the configuration directives to instruct the server how to # serve pages over an https connection. For detailing information about these # directives see <URL:[httpd.apache.org]; # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. #
# # 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 file:/dev/random 512 #SSLRandomSeed startup file:/dev/urandom 512 #SSLRandomSeed connect file:/dev/random 512 #SSLRandomSeed connect file:/dev/urandom 512
# # When we also provide SSL we have to listen to the # standard HTTP port (see above) and to the HTTPS port # # Note: Configurations that use IPv6 but not IPv4-mapped addresses need two # Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443" # Listen 443
## ## 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 a internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog builtin
# Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds). #SSLSessionCache "dbm:c:/apache2/logs/ssl_scache" SSLSessionCache "shmcb:c:/apache2/logs/ssl_scache(512000)" #SSLSessionCache "shmcb:C:/wamp/bin/Apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)" SSLSessionCacheTimeout 300
# Semaphore: # Configure the path to the mutual exclusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex default
## ## SSL Virtual Host Context ##
<VirtualHost _default_:443>
# General setup for the virtual host DocumentRoot "c:/apache2/htdocs" ServerName www.example.com:443 ServerAdmin admin@example.com ErrorLog "c:/apache2/logs/error.log" TransferLog "c:/apache2/logs/access.log"
# General setup for the virtual host #DocumentRoot "C:/wamp/www/ssl" #ServerName PASS:443 #ServerAdmin admin@localhost #ErrorLog "C:/wamp/bin/Apache/apache2.2.22/conf/ssl/logs/ssl_error.log" #TransferLog "C:/wamp/bin/Apache/apache2.2.22/conf/ssl/logs/ssl_access.log"
# SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on
# SSL Protocol support: # List the protocol versions which clients are allowed to # connect with. Disable SSLv2 by default (cf. RFC 6176). 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 HIGH:MEDIUM:!aNULL:!MD5
# Speed-optimized SSL Cipher configuration: # If speed is your main concern (on busy HTTPS servers e.g.), # you might want to force clients to specific, performance # optimized ciphers. In this case, prepend those ciphers # to the SSLCipherSuite list, and enable SSLHonorCipherOrder. # Caveat: by giving precedence to RC4-SHA and AES128-SHA # (as in the example below), most connections will no longer # have perfect forward secrecy - if the server's key is # compromised, captures of past or future traffic must be # considered compromised, too. #SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5 #SSLHonorCipherOrder on
# 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. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) SSLCertificateFile "c:/apache2/conf/server.crt" #SSLCertificateFile "C:/wamp/bin/Apache/apache2.2.22/conf/ssl/PASS.crt" #SSLCertificateFile "c:/apache2/conf/server-dsa.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 "c:/apache2/conf/server.key" #SSLCertificateKeyFile "C:/wamp/bin/Apache/apache2.2.22/conf/ssl/pass.key" #SSLCertificateKeyFile "c:/apache2/conf/server-dsa.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 "c:/apache2/conf/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. #SSLCACertificatePath "c:/apache2/conf/ssl.crt" #SSLCACertificateFile "c:/apache2/conf/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 "c:/apache2/conf/ssl.crl" #SSLCARevocationFile "c:/apache2/conf/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 "c:/apache2/cgi-bin"> SSLOptions +StdEnvVars </Directory>
#<Directory "A:/Workspace"> #SSLOptions +StdEnvVars #Options Indexes FollowSymLinks MultiViews #AllowOverride All #Order allow,deny #allow from all #</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-5]" \ 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 "c:/apache2/logs/ssl_request.log" \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" #CustomLog "C:/wamp/logs/ssl_request.log" \"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" #</VirtualHost>
Peut-être que cela peut vous aider voici l'organisation de mon dossier bin/ en image: [hpics.li]
Modifie 1 fois. Derniere modification le 04/04/2013 à 20:29 par sGendt.
sGendt a écrit: ------------------------------------------------------- > (Tous les modifications que j'avais effectué suite au topic sont commentées, elles se trouvent en dessous des originales): > SSLSessionCache "shmcb:c:/apache2/logs/ssl_scache(512000)" > #SSLSessionCache "shmcb:C:/wamp/bin/Apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)" -------------------------------------------------------
Ma valeur à moi c'est: #SSLSessionCache "shmcb:C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)". Et oui j'ai tout commenté, il faut bien que je travaille en attendant de résoudre le problème.
Par expérience ça ne coûte rien de vérifier les chemins et ça résout souvent des problèmes, je vais donc suivre votre conseil.
Edit:
Bon j'ai vérifié tous mes chemins, il y avait une erreur de majuscule Apache au lieu de apache(pas très grave sous windows mais plus embêtant sous linux), ex:
SSLSessionCache "shmcb:C:/wamp/bin/Apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)" au lieu de SSLSessionCache "shmcb:C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)"
Je les ai tous modifié j'ai dé-commenté la ligne, dans httpd.conf: Include conf/extra/httpd-ssl.conf
Wamp ne fonctionne plus et ne me fais plus de log à nouveau.
Je ne sais pas si c'est bien mais j'ai mis le SSL sur tout mon workspace:
# General setup for the virtual host DocumentRoot "A:/Workspace/" ServerName PASS:443 ServerAdmin admin@localhost ErrorLog "C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_error.log" TransferLog "C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_access.log"
puis
<Directory "A:/Workspace"> SSLOptions +StdEnvVars Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory>
Et j'ai déjà un vhosts sur le localhost dans httpd-vhosts.conf
# # This is the Apache server configuration file providing SSL support. # It contains the configuration directives to instruct the server how to # serve pages over an https connection. For detailing information about these # directives see <URL:[httpd.apache.org]; # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. #
# # 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 file:/dev/random 512 #SSLRandomSeed startup file:/dev/urandom 512 #SSLRandomSeed connect file:/dev/random 512 #SSLRandomSeed connect file:/dev/urandom 512
# # When we also provide SSL we have to listen to the # standard HTTP port (see above) and to the HTTPS port # # Note: Configurations that use IPv6 but not IPv4-mapped addresses need two # Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443" # Listen 443
## ## 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 a internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog builtin
# Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds). #SSLSessionCache "dbm:c:/apache2/logs/ssl_scache" #SSLSessionCache "shmcb:c:/apache2/logs/ssl_scache(512000)" SSLSessionCache "shmcb:C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_scache(512000)" SSLSessionCacheTimeout 300
# Semaphore: # Configure the path to the mutual exclusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex default
## ## SSL Virtual Host Context ##
<VirtualHost _default_:443>
# General setup for the virtual host #DocumentRoot "c:/apache2/htdocs" #ServerName www.example.com:443 #ServerAdmin admin@example.com #ErrorLog "c:/apache2/logs/error.log" #TransferLog "c:/apache2/logs/access.log"
# General setup for the virtual host DocumentRoot "A:/Workspace/" ServerName PASS:443 ServerAdmin admin@localhost ErrorLog "C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_error.log" TransferLog "C:/wamp/bin/apache/apache2.2.22/conf/ssl/logs/ssl_access.log"
# SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on
# SSL Protocol support: # List the protocol versions which clients are allowed to # connect with. Disable SSLv2 by default (cf. RFC 6176). 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 HIGH:MEDIUM:!aNULL:!MD5
# Speed-optimized SSL Cipher configuration: # If speed is your main concern (on busy HTTPS servers e.g.), # you might want to force clients to specific, performance # optimized ciphers. In this case, prepend those ciphers # to the SSLCipherSuite list, and enable SSLHonorCipherOrder. # Caveat: by giving precedence to RC4-SHA and AES128-SHA # (as in the example below), most connections will no longer # have perfect forward secrecy - if the server's key is # compromised, captures of past or future traffic must be # considered compromised, too. #SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5 #SSLHonorCipherOrder on
# 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. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) #SSLCertificateFile "c:/apache2/conf/server.crt" SSLCertificateFile "C:/wamp/bin/apache/apache2.2.22/conf/ssl/PASS.crt" #SSLCertificateFile "c:/apache2/conf/server-dsa.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 "c:/apache2/conf/server.key" SSLCertificateKeyFile "C:/wamp/bin/apache/apache2.2.22/conf/ssl/pass.key" #SSLCertificateKeyFile "c:/apache2/conf/server-dsa.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 "c:/apache2/conf/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. #SSLCACertificatePath "c:/apache2/conf/ssl.crt" #SSLCACertificateFile "c:/apache2/conf/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 "c:/apache2/conf/ssl.crl" #SSLCARevocationFile "c:/apache2/conf/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 "c:/apache2/cgi-bin"> # SSLOptions +StdEnvVars #</Directory>
<Directory "A:/Workspace"> SSLOptions +StdEnvVars Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </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-5]" \ 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 "c:/apache2/logs/ssl_request.log" \ # "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" CustomLog "C:/wamp/logs/ssl_request.log" \"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost>
Merci à vous pour votre soutien.
Modifie 5 fois. Derniere modification le 05/04/2013 à 11:29 par sGendt.
J'espère que c'est ce que vous attendiez, je suis aller dans: GEstion de l'ordinateur > outils système > observateur d'événements > événements de la page de résumé.
Voici la liste des erreurs de ce jour:
Niveau Date et heure Source ID de l’événement Catégorie de la tâche Erreur 05/04/2013 12:30:18 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Warning: DocumentRoot [A:/Workspace/JVNET/www/ad] does not exist ." Erreur 05/04/2013 11:24:49 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> CustomLog takes two or three arguments, a file name, a custom log format string or format name, and an optional ""env="" clause (see docs) ." Erreur 05/04/2013 11:24:49 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Syntax error on line 266 of C:/wamp/bin/apache/apache2.2.22/conf/extra/httpd-ssl.conf: ." Erreur 05/04/2013 11:24:49 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Warning: DocumentRoot [A:/Workspace/JVNET/www/ad] does not exist ." Erreur 05/04/2013 11:23:57 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> CustomLog takes two or three arguments, a file name, a custom log format string or format name, and an optional ""env="" clause (see docs) ." Erreur 05/04/2013 11:23:57 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Syntax error on line 266 of C:/wamp/bin/apache/apache2.2.22/conf/extra/httpd-ssl.conf: ." Erreur 05/04/2013 11:23:57 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Warning: DocumentRoot [A:/Workspace/JVNET/www/ad] does not exist ." Erreur 05/04/2013 11:03:51 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> CustomLog takes two or three arguments, a file name, a custom log format string or format name, and an optional ""env="" clause (see docs) ." Erreur 05/04/2013 11:03:51 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Syntax error on line 266 of C:/wamp/bin/apache/apache2.2.22/conf/extra/httpd-ssl.conf: ." Erreur 05/04/2013 11:03:51 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Warning: DocumentRoot [A:/Workspace/JVNET/www/ad] does not exist ." Erreur 05/04/2013 11:02:32 Apache Service 3299 Aucun "The Apache service named reported the following error: >>> Warning: DocumentRoot [A:/Workspace/JVNET/www/ad] does not exist ."
J'ai relancé wamp, il n'a pas démarré je suis retourné voir le journal d'erreur windows il n'y en avait pas d'erreur suite à ce restart, par contre le point positif c'est que Apache recommence à faire des logs, voici le dernier log:
[Fri Apr 05 14:51:03 2013] [notice] Parent: Received shutdown signal -- Shutting down the server. [Fri Apr 05 14:51:03 2013] [notice] Child 7012: Exit event signaled. Child process is ending. [Fri Apr 05 14:51:04 2013] [notice] Child 7012: Released the start mutex [Fri Apr 05 14:51:05 2013] [notice] Child 7012: All worker threads have exited. [Fri Apr 05 14:51:05 2013] [notice] Child 7012: Child process is exiting [Fri Apr 05 14:51:05 2013] [notice] Parent: Child process exited successfully. [Fri Apr 05 14:51:09 2013] [error] Init: SSLPassPhraseDialog builtin is not supported on Win32 (key file C:/wamp/bin/apache/apache2.2.22/conf/ssl/pass.key)
Merci ça avance, j'ai déjà eu erreur semblable à celle-ci (Init: SSLPassPhraseDialog builtin is not supported on Win32 (key file C:/wamp/bin/apache/apache2.2.22/conf/ssl/pass.key)) en installant memcache.
Pour memcache c'était le php_memcache.dll et le memcache.exe qui n'étaient pas bon. Est-ce que ça peut être php_openssl.dll et C:\wamp\bin\apache\apache2.2.22\bin\openssl.exe qui ne sont pas bon pour windows 8 64bits?
Modifie 3 fois. Derniere modification le 05/04/2013 à 15:05 par sGendt.
C'est la même erreur que Nas dans le topic que j'ai suivi au départ: [forum.wampserver.com].
Un article parle de ça sur un autre site [www.entrust.net], c'est identique aux préconisations de Nas:
Ce qu'il va falloir faire:
Enlever le chiffrement de la clé privée RSA (tout en conservant le fichier original) Remarque dans le fichier de conf httpd-ssl.conf mettre un # devant de la directive SSLPassPhraseDialog .
Étapes:
1. Faites une copie de la clé privée et l'appeler "server.key.org" dans le répertoire C:\wamp\bin\apache\apachex.x.xx\bin
2. Utilisez la commande OpenSSL pour supprimer la pass phrase: openssl rsa -in server.key.org -out server.key (Il faut se positionner dans le répertoire C:\wamp\bin\apache\apachex.x.xx\bin avec la commande cd)
Exemple:
c:\wamp\bin\apache\apache2.2.22\bin>openssl rsa -in pass.key.org -out pass.key Enter pass phrase for pass.key.org: writing RSA key
3. Déplacer la nouvelle clé de C:\wamp\bin\apache\apachex.x.xx\bin\PASS.key dans le répertoire C:\wamp\bin\apache\apache2.2.22\conf\ssl\PASS.key.
4.Trouvez la directive "SSLPassPhraseDialog" et mettez un # devant pour commenter la ligne.
5. Redémarrez Wamp, normalement ça fonctionne.
Voilà pour ma participation quelque peu identique à celle de Nas mais un peu plus détaillé, avec l'aide Bagu.
--------------------------------------------
Il me reste une dernière question: Comment gérer le ssl uniquement pour certains virtualhosts ou uniquement pour certains répertoires? (j'ai le problème que dans ce sujet [forum.wampserver.com])