74 lines
3.5 KiB
Plaintext
74 lines
3.5 KiB
Plaintext
<IfModule mod_ssl.c>
|
|
# 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 builtin
|
|
SSLRandomSeed connect builtin
|
|
#SSLRandomSeed startup file:/dev/random 512
|
|
#SSLRandomSeed startup file:/dev/urandom 512
|
|
#SSLRandomSeed connect file:/dev/random 512
|
|
#SSLRandomSeed connect file:/dev/urandom 512
|
|
|
|
# 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 none
|
|
#SSLSessionCache shmht:/var/run/apache2/ssl_scache(512000)
|
|
#SSLSessionCache shmcb:/var/run/apache2/ssl_scache(512000)
|
|
SSLSessionCache dbm:/var/run/apache2/ssl_scache
|
|
SSLSessionCacheTimeout 300
|
|
|
|
# Semaphore:
|
|
# Configure the path to the mutual exclusion semaphore the
|
|
# SSL engine uses internally for inter-process synchronization.
|
|
SSLMutex file:/var/run/apache2/ssl_mutex
|
|
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
|
|
|
|
# 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
|
|
</IfModule>
|