Advertisement
Guest User

Untitled

a guest
Aug 4th, 2016
118
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.27 KB | None | 0 0
  1. #
  2. # When we also provide SSL we have to listen to the
  3. # the HTTPS port in addition.
  4. #
  5. Listen 443 https
  6.  
  7. ##
  8. ## SSL Global Context
  9. ##
  10. ## All SSL configuration in this context applies both to
  11. ## the main server and all SSL-enabled virtual hosts.
  12. ##
  13.  
  14. # Pass Phrase Dialog:
  15. # Configure the pass phrase gathering process.
  16. # The filtering dialog program (`builtin' is a internal
  17. # terminal dialog) has to provide the pass phrase on stdout.
  18. SSLPassPhraseDialog exec:/usr/libexec/httpd-ssl-pass-dialog
  19.  
  20. # Inter-Process Session Cache:
  21. # Configure the SSL Session Cache: First the mechanism
  22. # to use and second the expiring timeout (in seconds).
  23. SSLSessionCache shmcb:/run/httpd/sslcache(512000)
  24. SSLSessionCacheTimeout 300
  25.  
  26. # Pseudo Random Number Generator (PRNG):
  27. # Configure one or more sources to seed the PRNG of the
  28. # SSL library. The seed data should be of good random quality.
  29. # WARNING! On some platforms /dev/random blocks if not enough entropy
  30. # is available. This means you then cannot use the /dev/random device
  31. # because it would lead to very long connection times (as long as
  32. # it requires to make more entropy available). But usually those
  33. # platforms additionally provide a /dev/urandom device which doesn't
  34. # block. So, if available, use this one instead. Read the mod_ssl User
  35. # Manual for more details.
  36. SSLRandomSeed startup file:/dev/urandom 256
  37. SSLRandomSeed connect builtin
  38. #SSLRandomSeed startup file:/dev/random 512
  39. #SSLRandomSeed connect file:/dev/random 512
  40. #SSLRandomSeed connect file:/dev/urandom 512
  41.  
  42. #
  43. # Use "SSLCryptoDevice" to enable any supported hardware
  44. # accelerators. Use "openssl engine -v" to list supported
  45. # engine names. NOTE: If you enable an accelerator and the
  46. # server does not start, consult the error logs and ensure
  47. # your accelerator is functioning properly.
  48. #
  49. SSLCryptoDevice builtin
  50. #SSLCryptoDevice ubsec
  51.  
  52. ##
  53. ## SSL Virtual Host Context
  54. ##
  55.  
  56. <VirtualHost _default_:443>
  57.  
  58. # General setup for the virtual host, inherited from global configuration
  59. #DocumentRoot "/var/www/html"
  60. #ServerName www.example.com:443
  61.  
  62. # Use separate log files for the SSL virtual host; note that LogLevel
  63. # is not inherited from httpd.conf.
  64. ErrorLog logs/ssl_error_log
  65. TransferLog logs/ssl_access_log
  66. LogLevel warn
  67.  
  68. # SSL Engine Switch:
  69. # Enable/Disable SSL for this virtual host.
  70. SSLEngine on
  71.  
  72. # SSL Protocol support:
  73. # List the enable protocol levels with which clients will be able to
  74. # connect. Disable SSLv2 access by default:
  75. #SSLProtocol All -SSLv2 -SSLv3
  76. SSLProtocol all -SSLv2 -SSLv3
  77.  
  78. # SSL Cipher Suite:
  79. # List the ciphers that the client is permitted to negotiate.
  80. # See the mod_ssl documentation for a complete list.
  81. #SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
  82. SSLCipherSuite EECDH+AES:AES256-SHA:AES128-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH:!EXP:!SRP:!DSS:!LOW;
  83. # Speed-optimized SSL Cipher configuration:
  84. # If speed is your main concern (on busy HTTPS servers e.g.),
  85. # you might want to force clients to specific, performance
  86. # optimized ciphers. In this case, prepend those ciphers
  87. # to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
  88. # Caveat: by giving precedence to RC4-SHA and AES128-SHA
  89. # (as in the example below), most connections will no longer
  90. # have perfect forward secrecy - if the server's key is
  91. # compromised, captures of past or future traffic must be
  92. # considered compromised, too.
  93. #SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
  94. SSLHonorCipherOrder on
  95.  
  96. # Server Certificate:
  97. # Point SSLCertificateFile at a PEM encoded certificate. If
  98. # the certificate is encrypted, then you will be prompted for a
  99. # pass phrase. Note that a kill -HUP will prompt again. A new
  100. # certificate can be generated using the genkey(1) command.
  101. SSLCertificateFile /etc/pki/tls/certs/localhost.crt
  102.  
  103. # Server Private Key:
  104. # If the key is not combined with the certificate, use this
  105. # directive to point at the key file. Keep in mind that if
  106. # you've both a RSA and a DSA private key you can configure
  107. # both in parallel (to also allow the use of DSA ciphers, etc.)
  108. SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
  109.  
  110. # Server Certificate Chain:
  111. # Point SSLCertificateChainFile at a file containing the
  112. # concatenation of PEM encoded CA certificates which form the
  113. # certificate chain for the server certificate. Alternatively
  114. # the referenced file can be the same as SSLCertificateFile
  115. # when the CA certificates are directly appended to the server
  116. # certificate for convinience.
  117. #SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
  118.  
  119. # Certificate Authority (CA):
  120. # Set the CA certificate verification path where to find CA
  121. # certificates for client authentication or alternatively one
  122. # huge file containing all of them (file must be PEM encoded)
  123. #SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
  124.  
  125. # Client Authentication (Type):
  126. # Client certificate verification type and depth. Types are
  127. # none, optional, require and optional_no_ca. Depth is a
  128. # number which specifies how deeply to verify the certificate
  129. # issuer chain before deciding the certificate is not valid.
  130. #SSLVerifyClient none
  131. #SLVerifyDepth 1
  132.  
  133. # Access Control:
  134. # With SSLRequire you can do per-directory access control based
  135. # on arbitrary complex boolean expressions containing server
  136. # variable checks and other lookup directives. The syntax is a
  137. # mixture between C and Perl. See the mod_ssl documentation
  138. # for more details.
  139. #<Location />
  140. #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
  141. # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
  142. # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
  143. # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
  144. # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
  145. # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
  146. #</Location>
  147.  
  148. # SSL Engine Options:
  149. # Set various options for the SSL engine.
  150. # o FakeBasicAuth:
  151. # Translate the client X.509 into a Basic Authorisation. This means that
  152. # the standard Auth/DBMAuth methods can be used for access control. The
  153. # user name is the `one line' version of the client's X.509 certificate.
  154. # Note that no password is obtained from the user. Every entry in the user
  155. # file needs this password: `xxj31ZMTZzkVA'.
  156. # o ExportCertData:
  157. # This exports two additional environment variables: SSL_CLIENT_CERT and
  158. # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
  159. # server (always existing) and the client (only existing when client
  160. # authentication is used). This can be used to import the certificates
  161. # into CGI scripts.
  162. # o StdEnvVars:
  163. # This exports the standard SSL/TLS related `SSL_*' environment variables.
  164. # Per default this exportation is switched off for performance reasons,
  165. # because the extraction step is an expensive operation and is usually
  166. # useless for serving static content. So one usually enables the
  167. # exportation for CGI and SSI requests only.
  168. # o StrictRequire:
  169. # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
  170. # under a "Satisfy any" situation, i.e. when it applies access is denied
  171. # and no other module can change it.
  172. # o OptRenegotiate:
  173. # This enables optimized SSL connection renegotiation handling when SSL
  174. # directives are used in per-directory context.
  175. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
  176. <Files ~ "\.(cgi|shtml|phtml|php3?)$">
  177. SSLOptions +StdEnvVars
  178. </Files>
  179. <Directory "/var/www/cgi-bin">
  180. SSLOptions +StdEnvVars
  181. </Directory>
  182.  
  183. # SSL Protocol Adjustments:
  184. # The safe and default but still SSL/TLS standard compliant shutdown
  185. # approach is that mod_ssl sends the close notify alert but doesn't wait for
  186. # the close notify alert from client. When you need a different shutdown
  187. # approach you can use one of the following variables:
  188. # o ssl-unclean-shutdown:
  189. # This forces an unclean shutdown when the connection is closed, i.e. no
  190. # SSL close notify alert is send or allowed to received. This violates
  191. # the SSL/TLS standard but is needed for some brain-dead browsers. Use
  192. # this when you receive I/O errors because of the standard approach where
  193. # mod_ssl sends the close notify alert.
  194. # o ssl-accurate-shutdown:
  195. # This forces an accurate shutdown when the connection is closed, i.e. a
  196. # SSL close notify alert is send and mod_ssl waits for the close notify
  197. # alert of the client. This is 100% SSL/TLS standard compliant, but in
  198. # practice often causes hanging connections with brain-dead browsers. Use
  199. # this only for browsers where you know that their SSL implementation
  200. # works correctly.
  201. # Notice: Most problems of broken clients are also related to the HTTP
  202. # keep-alive facility, so you usually additionally want to disable
  203. # keep-alive for those clients, too. Use variable "nokeepalive" for this.
  204. # Similarly, one has to force some clients to use HTTP/1.0 to workaround
  205. # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
  206. # "force-response-1.0" for this.
  207. BrowserMatch "MSIE [2-5]" \
  208. nokeepalive ssl-unclean-shutdown \
  209. downgrade-1.0 force-response-1.0
  210.  
  211. # Per-Server Logging:
  212. # The home of a custom SSL log file. Use this when you want a
  213. # compact non-error SSL logfile on a virtual host basis.
  214. CustomLog logs/ssl_request_log \
  215. "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
  216.  
  217. </VirtualHost>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement