3 ServerAdmin webmaster@dehnerts.com
4 ServerName olinda.mit.edu
5 ServerAlias svn.dehnerts.com svn.dehnert.arctic.org
6 ServerAlias www.dehnerts.com www.dehnert.arctic.org
10 Options FollowSymLinks
14 Options Indexes FollowSymLinks MultiViews
20 ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
21 <Directory "/usr/lib/cgi-bin">
23 Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
28 ErrorLog /var/log/apache2/error.log
30 # Possible values include: debug, info, notice, warn, error, crit,
34 CustomLog /var/log/apache2/ssl_access.log combined
36 Alias /doc/ "/usr/share/doc/"
37 <Directory "/usr/share/doc/">
38 Options Indexes MultiViews FollowSymLinks
42 Allow from 127.0.0.0/255.0.0.0 ::1/128
46 # Enable/Disable SSL for this virtual host.
49 # A self-signed (snakeoil) certificate can be created by installing
50 # the ssl-cert package. See
51 # /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
52 # If both key and certificate are stored in the same file, only the
53 # SSLCertificateFile directive is needed.
54 SSLCertificateFile /etc/ssl/certs/general-web.crt
55 SSLCertificateKeyFile /etc/ssl/private/general-web.key
57 # Server Certificate Chain:
58 # Point SSLCertificateChainFile at a file containing the
59 # concatenation of PEM encoded CA certificates which form the
60 # certificate chain for the server certificate. Alternatively
61 # the referenced file can be the same as SSLCertificateFile
62 # when the CA certificates are directly appended to the server
63 # certificate for convinience.
64 #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
66 # Certificate Authority (CA):
67 # Set the CA certificate verification path where to find CA
68 # certificates for client authentication or alternatively one
69 # huge file containing all of them (file must be PEM encoded)
70 # Note: Inside SSLCACertificatePath you need hash symlinks
71 # to point to the certificate files. Use the provided
72 # Makefile to update the hash symlinks after changes.
73 #SSLCACertificatePath /etc/ssl/certs/
74 #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
76 # Certificate Revocation Lists (CRL):
77 # Set the CA revocation path where to find CA CRLs for client
78 # authentication or alternatively one huge file containing all
79 # of them (file must be PEM encoded)
80 # Note: Inside SSLCARevocationPath you need hash symlinks
81 # to point to the certificate files. Use the provided
82 # Makefile to update the hash symlinks after changes.
83 #SSLCARevocationPath /etc/apache2/ssl.crl/
84 #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
86 # Client Authentication (Type):
87 # Client certificate verification type and depth. Types are
88 # none, optional, require and optional_no_ca. Depth is a
89 # number which specifies how deeply to verify the certificate
90 # issuer chain before deciding the certificate is not valid.
91 #SSLVerifyClient require
95 # With SSLRequire you can do per-directory access control based
96 # on arbitrary complex boolean expressions containing server
97 # variable checks and other lookup directives. The syntax is a
98 # mixture between C and Perl. See the mod_ssl documentation
101 #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
102 # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
103 # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
104 # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
105 # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
106 # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
109 # SSL Engine Options:
110 # Set various options for the SSL engine.
112 # Translate the client X.509 into a Basic Authorisation. This means that
113 # the standard Auth/DBMAuth methods can be used for access control. The
114 # user name is the `one line' version of the client's X.509 certificate.
115 # Note that no password is obtained from the user. Every entry in the user
116 # file needs this password: `xxj31ZMTZzkVA'.
118 # This exports two additional environment variables: SSL_CLIENT_CERT and
119 # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
120 # server (always existing) and the client (only existing when client
121 # authentication is used). This can be used to import the certificates
124 # This exports the standard SSL/TLS related `SSL_*' environment variables.
125 # Per default this exportation is switched off for performance reasons,
126 # because the extraction step is an expensive operation and is usually
127 # useless for serving static content. So one usually enables the
128 # exportation for CGI and SSI requests only.
130 # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
131 # under a "Satisfy any" situation, i.e. when it applies access is denied
132 # and no other module can change it.
134 # This enables optimized SSL connection renegotiation handling when SSL
135 # directives are used in per-directory context.
136 #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
137 <FilesMatch "\.(cgi|shtml|phtml|php)$">
138 SSLOptions +StdEnvVars
140 <Directory /usr/lib/cgi-bin>
141 SSLOptions +StdEnvVars
144 # SSL Protocol Adjustments:
145 # The safe and default but still SSL/TLS standard compliant shutdown
146 # approach is that mod_ssl sends the close notify alert but doesn't wait for
147 # the close notify alert from client. When you need a different shutdown
148 # approach you can use one of the following variables:
149 # o ssl-unclean-shutdown:
150 # This forces an unclean shutdown when the connection is closed, i.e. no
151 # SSL close notify alert is send or allowed to received. This violates
152 # the SSL/TLS standard but is needed for some brain-dead browsers. Use
153 # this when you receive I/O errors because of the standard approach where
154 # mod_ssl sends the close notify alert.
155 # o ssl-accurate-shutdown:
156 # This forces an accurate shutdown when the connection is closed, i.e. a
157 # SSL close notify alert is send and mod_ssl waits for the close notify
158 # alert of the client. This is 100% SSL/TLS standard compliant, but in
159 # practice often causes hanging connections with brain-dead browsers. Use
160 # this only for browsers where you know that their SSL implementation
162 # Notice: Most problems of broken clients are also related to the HTTP
163 # keep-alive facility, so you usually additionally want to disable
164 # keep-alive for those clients, too. Use variable "nokeepalive" for this.
165 # Similarly, one has to force some clients to use HTTP/1.0 to workaround
166 # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
167 # "force-response-1.0" for this.
168 BrowserMatch ".*MSIE.*" \
169 nokeepalive ssl-unclean-shutdown \
170 downgrade-1.0 force-response-1.0