httpd-ssl_uwamp.conf 9.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231
  1. #
  2. # This is the Apache server configuration file providing SSL support.
  3. # It contains the configuration directives to instruct the server how to
  4. # serve pages over an https connection. For detailing information about these
  5. # directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
  6. #
  7. # Do NOT simply read the instructions in here without understanding
  8. # what they do. They're here only as hints or reminders. If you are unsure
  9. # consult the online docs. You have been warned.
  10. #
  11. #
  12. # Pseudo Random Number Generator (PRNG):
  13. # Configure one or more sources to seed the PRNG of the SSL library.
  14. # The seed data should be of good random quality.
  15. # WARNING! On some platforms /dev/random blocks if not enough entropy
  16. # is available. This means you then cannot use the /dev/random device
  17. # because it would lead to very long connection times (as long as
  18. # it requires to make more entropy available). But usually those
  19. # platforms additionally provide a /dev/urandom device which doesn't
  20. # block. So, if available, use this one instead. Read the mod_ssl User
  21. # Manual for more details.
  22. #
  23. #SSLRandomSeed startup file:/dev/random 512
  24. #SSLRandomSeed startup file:/dev/urandom 512
  25. #SSLRandomSeed connect file:/dev/random 512
  26. #SSLRandomSeed connect file:/dev/urandom 512
  27. #
  28. # When we also provide SSL we have to listen to the
  29. # standard HTTP port (see above) and to the HTTPS port
  30. #
  31. # Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
  32. # Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
  33. #
  34. Listen 443
  35. ##
  36. ## SSL Global Context
  37. ##
  38. ## All SSL configuration in this context applies both to
  39. ## the main server and all SSL-enabled virtual hosts.
  40. ##
  41. #
  42. # Some MIME-types for downloading Certificates and CRLs
  43. #
  44. AddType application/x-x509-ca-cert .crt
  45. AddType application/x-pkcs7-crl .crl
  46. # Pass Phrase Dialog:
  47. # Configure the pass phrase gathering process.
  48. # The filtering dialog program (`builtin' is a internal
  49. # terminal dialog) has to provide the pass phrase on stdout.
  50. SSLPassPhraseDialog builtin
  51. # Inter-Process Session Cache:
  52. # Configure the SSL Session Cache: First the mechanism
  53. # to use and second the expiring timeout (in seconds).
  54. #SSLSessionCache "dbm:{APACHEPATH}/logs/ssl_scache"
  55. SSLSessionCache "shmcb:{APACHEPATH}/logs/ssl_scache(512000)"
  56. SSLSessionCacheTimeout 300
  57. # Semaphore:
  58. # Configure the path to the mutual exclusion semaphore the
  59. # SSL engine uses internally for inter-process synchronization.
  60. SSLMutex default
  61. ##
  62. ## SSL Virtual Host Context
  63. ##
  64. <VirtualHost _default_:443>
  65. # General setup for the virtual host
  66. DocumentRoot "{APACHEPATH}/htdocs"
  67. ServerName test:443
  68. ServerAdmin test@toto.com
  69. ErrorLog "{APACHEPATH}/logs/error.log"
  70. TransferLog "{APACHEPATH}/logs/access.log"
  71. # SSL Engine Switch:
  72. # Enable/Disable SSL for this virtual host.
  73. SSLEngine on
  74. # SSL Cipher Suite:
  75. # List the ciphers that the client is permitted to negotiate.
  76. # See the mod_ssl documentation for a complete list.
  77. SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
  78. # Server Certificate:
  79. # Point SSLCertificateFile at a PEM encoded certificate. If
  80. # the certificate is encrypted, then you will be prompted for a
  81. # pass phrase. Note that a kill -HUP will prompt again. Keep
  82. # in mind that if you have both an RSA and a DSA certificate you
  83. # can configure both in parallel (to also allow the use of DSA
  84. # ciphers, etc.)
  85. SSLCertificateFile "{APACHEPATH}/conf/server.crt"
  86. #SSLCertificateFile "{APACHEPATH}/conf/server-dsa.crt"
  87. # Server Private Key:
  88. # If the key is not combined with the certificate, use this
  89. # directive to point at the key file. Keep in mind that if
  90. # you've both a RSA and a DSA private key you can configure
  91. # both in parallel (to also allow the use of DSA ciphers, etc.)
  92. SSLCertificateKeyFile "{APACHEPATH}/conf/server.key"
  93. #SSLCertificateKeyFile "{APACHEPATH}/conf/server-dsa.key"
  94. # Server Certificate Chain:
  95. # Point SSLCertificateChainFile at a file containing the
  96. # concatenation of PEM encoded CA certificates which form the
  97. # certificate chain for the server certificate. Alternatively
  98. # the referenced file can be the same as SSLCertificateFile
  99. # when the CA certificates are directly appended to the server
  100. # certificate for convinience.
  101. #SSLCertificateChainFile "{APACHEPATH}/conf/server-ca.crt"
  102. # Certificate Authority (CA):
  103. # Set the CA certificate verification path where to find CA
  104. # certificates for client authentication or alternatively one
  105. # huge file containing all of them (file must be PEM encoded)
  106. # Note: Inside SSLCACertificatePath you need hash symlinks
  107. # to point to the certificate files. Use the provided
  108. # Makefile to update the hash symlinks after changes.
  109. #SSLCACertificatePath "{APACHEPATH}/conf/ssl.crt"
  110. #SSLCACertificateFile "{APACHEPATH}/conf/ssl.crt/ca-bundle.crt"
  111. # Certificate Revocation Lists (CRL):
  112. # Set the CA revocation path where to find CA CRLs for client
  113. # authentication or alternatively one huge file containing all
  114. # of them (file must be PEM encoded)
  115. # Note: Inside SSLCARevocationPath you need hash symlinks
  116. # to point to the certificate files. Use the provided
  117. # Makefile to update the hash symlinks after changes.
  118. #SSLCARevocationPath "{APACHEPATH}/conf/ssl.crl"
  119. #SSLCARevocationFile "{APACHEPATH}/conf/ssl.crl/ca-bundle.crl"
  120. # Client Authentication (Type):
  121. # Client certificate verification type and depth. Types are
  122. # none, optional, require and optional_no_ca. Depth is a
  123. # number which specifies how deeply to verify the certificate
  124. # issuer chain before deciding the certificate is not valid.
  125. #SSLVerifyClient require
  126. #SSLVerifyDepth 10
  127. # Access Control:
  128. # With SSLRequire you can do per-directory access control based
  129. # on arbitrary complex boolean expressions containing server
  130. # variable checks and other lookup directives. The syntax is a
  131. # mixture between C and Perl. See the mod_ssl documentation
  132. # for more details.
  133. #<Location />
  134. #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
  135. # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
  136. # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
  137. # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
  138. # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
  139. # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
  140. #</Location>
  141. # SSL Engine Options:
  142. # Set various options for the SSL engine.
  143. # o FakeBasicAuth:
  144. # Translate the client X.509 into a Basic Authorisation. This means that
  145. # the standard Auth/DBMAuth methods can be used for access control. The
  146. # user name is the `one line' version of the client's X.509 certificate.
  147. # Note that no password is obtained from the user. Every entry in the user
  148. # file needs this password: `xxj31ZMTZzkVA'.
  149. # o ExportCertData:
  150. # This exports two additional environment variables: SSL_CLIENT_CERT and
  151. # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
  152. # server (always existing) and the client (only existing when client
  153. # authentication is used). This can be used to import the certificates
  154. # into CGI scripts.
  155. # o StdEnvVars:
  156. # This exports the standard SSL/TLS related `SSL_*' environment variables.
  157. # Per default this exportation is switched off for performance reasons,
  158. # because the extraction step is an expensive operation and is usually
  159. # useless for serving static content. So one usually enables the
  160. # exportation for CGI and SSI requests only.
  161. # o StrictRequire:
  162. # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
  163. # under a "Satisfy any" situation, i.e. when it applies access is denied
  164. # and no other module can change it.
  165. # o OptRenegotiate:
  166. # This enables optimized SSL connection renegotiation handling when SSL
  167. # directives are used in per-directory context.
  168. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
  169. <FilesMatch "\.(cgi|shtml|phtml|php)$">
  170. SSLOptions +StdEnvVars
  171. </FilesMatch>
  172. <Directory "{APACHEPATH}/cgi-bin">
  173. SSLOptions +StdEnvVars
  174. </Directory>
  175. # SSL Protocol Adjustments:
  176. # The safe and default but still SSL/TLS standard compliant shutdown
  177. # approach is that mod_ssl sends the close notify alert but doesn't wait for
  178. # the close notify alert from client. When you need a different shutdown
  179. # approach you can use one of the following variables:
  180. # o ssl-unclean-shutdown:
  181. # This forces an unclean shutdown when the connection is closed, i.e. no
  182. # SSL close notify alert is send or allowed to received. This violates
  183. # the SSL/TLS standard but is needed for some brain-dead browsers. Use
  184. # this when you receive I/O errors because of the standard approach where
  185. # mod_ssl sends the close notify alert.
  186. # o ssl-accurate-shutdown:
  187. # This forces an accurate shutdown when the connection is closed, i.e. a
  188. # SSL close notify alert is send and mod_ssl waits for the close notify
  189. # alert of the client. This is 100% SSL/TLS standard compliant, but in
  190. # practice often causes hanging connections with brain-dead browsers. Use
  191. # this only for browsers where you know that their SSL implementation
  192. # works correctly.
  193. # Notice: Most problems of broken clients are also related to the HTTP
  194. # keep-alive facility, so you usually additionally want to disable
  195. # keep-alive for those clients, too. Use variable "nokeepalive" for this.
  196. # Similarly, one has to force some clients to use HTTP/1.0 to workaround
  197. # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
  198. # "force-response-1.0" for this.
  199. BrowserMatch ".*MSIE.*" \
  200. nokeepalive ssl-unclean-shutdown \
  201. downgrade-1.0 force-response-1.0
  202. # Per-Server Logging:
  203. # The home of a custom SSL log file. Use this when you want a
  204. # compact non-error SSL logfile on a virtual host basis.
  205. CustomLog "{APACHEPATH}/logs/ssl_request.log" \
  206. "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
  207. </VirtualHost>