Onderwerp: SSL probleem

Ik heb de config files even online gezet
hier de link: http://www.adslnetwerk.com/conf
Hopelijk kan me iemand verder helpen?

Wat gebeurd er als je al die ifdefine dingen van ssl weghaalt? Pakt die hem dan wel?

En waarom gebruik je in je httpd.conf: <IfDefine mod_ssl.c> en in je ssl.conf <IfDefine SSL> ??

En verander in je ssl.conf

<VirtualHost _default_:443>

een in:

<VirtualHost EXTERN_IP_ADRES:443>

Ik zie overigens ook geen virtualhost voor de ssl config in de huidige configuratie. Wellicht handig om dat toe te voegen??

Origineel geplaatst door Deimos
Wat gebeurd er als je al die ifdefine dingen van ssl weghaalt? Pakt die hem dan wel?

En waarom gebruik je in je httpd.conf: <IfDefine mod_ssl.c> en in je ssl.conf <IfDefine SSL> ??

En verander in je ssl.conf

<VirtualHost _default_:443>

een in:

<VirtualHost EXTERN_IP_ADRES:443>

Als mod_ssl geladen dan laad hij ook de ssl.conf anders niet
Kan hem er ook met een include erinzetten maar het effect is hetzelfde.

Ik zou het gewoon weg laten. Nu voer je het namelijk dubbel uit. Eerst kijk je in je httpd.conf of mod_ssl module actief is. Zo ja, dan wordt er in de ssl.conf wederom gekeken of deze actief is.

Origineel geplaatst door Deimos
Ik zie overigens ook geen virtualhost voor de ssl config in de huidige configuratie. Wellicht handig om dat toe te voegen??

Ok gedaan hieronder de huidige config maar geen verbeteringen:

#
# 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:http://httpd.apache.org/docs-2.0/mod/mod_ssl.html>
#
# For the moment, see <URL:http://www.modssl.org/docs/> for this info.
# The documents are still being prepared from material donated by the
# modssl project.
#
# 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.
#
# Until documentation is completed, please check http://www.modssl.org/
# for additional config examples and module docmentation. Directives
# and features of mod_ssl are largely unchanged from the mod_ssl project
# for Apache 1.3.

#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
Listen 443

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common

##
## 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 none
#SSLSessionCache shmht:logs/ssl_scache(512000)
#SSLSessionCache shmcb:logs/ssl_scache(512000)
SSLSessionCache dbm:logs/ssl_scache
SSLSessionCacheTimeout 300

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
#SSLMutex file:logs/ssl_mutex
SSLMutex none

# 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

# Logging:
# The home of the dedicated SSL protocol logfile. Errors are
# additionally duplicated in the general error log file. Put
# this somewhere where it cannot be used for symlink attacks on
# a real server (i.e. somewhere where only root can write).
# Log levels are (ascending order: higher ones include lower ones):
# none, error, warn, info, trace, debug.
# SSLLog and SSLLogLevel doesn't exists since Apache 2.0.39 - Oswald
#SSLLog logs/ssl_engine_log
#SSLLogLevel info

##
## SSL Virtual Host Context
##

<VirtualHost 80.126.127.66:443>

# General setup for the virtual host
DocumentRoot "/opt/lampp/htdocs"
ServerName 80.126.127.66:443
ServerAdmin info@adslnetwerk.com
ErrorLog logs/error_log
TransferLog logs/access_log

# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on

# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSL v2:+EXP:+eNULL

# 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. A test
# certificate can be generated with `make certificate' under
# built time. Keep in mind that if you've both a RSA and a DSA
# certificate you can configure both in parallel (to also allow
# the use of DSA ciphers, etc.)
SSLCertificateFile /opt/lampp/etc/ssl.crt/server.crt
#SSLCertificateFile /opt/lampp/etc/ssl.crt/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 /opt/lampp/etc/ssl.key/server.key
#SSLCertificateKeyFile /opt/lampp/etc/ssl.key/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 /opt/lampp/etc/ssl.crt/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 /opt/lampp/etc/ssl.crt
#SSLCACertificateFile /opt/lampp/etc/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 /opt/lampp/etc/ssl.crl
#SSLCARevocationFile /opt/lampp/etc/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 CompatEnvVars:
# This exports obsolete environment variables for backward compatibility
# to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
# to provide compatibility to existing CGI scripts.
# 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 +CompatEnvVars +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/opt/lampp/cgi-bin">
SSLOptions +StdEnvVars
</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.
SetEnvIf User-Agent ".*MSIE.*" \
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 logs/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>

ServerName 80.126.127.66:443

volgens de manual moet deze hieraan voldoen:

ServerName directive
Syntax: ServerName fully-qualified-domain-name
Context: server config, virtual host
Status: core
The ServerName directive sets the hostname of the server; this is used when creating redirection URLs. If it is not specified, then the server attempts to deduce it from its own IP address; however this may not work reliably, or may not return the preferred hostname. For example:

ServerName www.example.com
would be used if the canonical (main) name of the actual machine were simple.example.com.
If you are using name-based virtual hosts, the ServerName inside a <VirtualHost> section specifies what hostname must appear in the request's Host: header to match this virtual host.

Deimos dit had ik al gedaan.. maar ook niet
Ik denk dat ik de fout gevonden heb, dit stond in de log:

RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

Origineel geplaatst door Herbert
Deimos dit had ik al gedaan.. maar ook niet
Ik denk dat ik de fout gevonden heb, dit stond in de log:

RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

Dat zal inderdaad je probleem zijn. Stom ook van me om niet gelijk te roepen: "Wat staat er in je logfile?". Logfiles... the key to success... of liever... the key to resolving not having success... ofzo

Mischien een stomme vraag?
Ik het mogelijk de server.key die op localhost staat te laten werken op www.domeinnaam.tld ?
Ik heb geprobeerd een nieuwe demo key te maken voor 1 jaar maar dan start apache niet in ssl

Dit is mogelijk, wat zeggen je error.logs deze keer?

Verder moet IMO de server evengoed gewoon starten ondanks dat de CN localhost is. Je behoort dan een error te krijgen bij het bezoeken van de site dat de CN niet hoort. Apache zelf hoort zich er niets van aan te trekken.

Origineel geplaatst door Deimos
Dit is mogelijk, wat zeggen je error.logs deze keer?

Verder moet IMO de server evengoed gewoon starten ondanks dat de CN localhost is. Je behoort dan een error te krijgen bij het bezoeken van de site dat de CN niet hoort. Apache zelf hoort zich er niets van aan te trekken.

Ik weet ook dat het normaal zou moeten werken maar SSL luisterd alleen op localhost en op het interne IP nummer.
En bij bijvoorbeeld: http://grc.com zegt die ook dat poort 443 openstaat.

Als poort 443 openstaat waarom kan die niks vinden dan??
Ik denk dat ik het maar opgeef na 1 week, dan maar geen SSL

Kan je nog eens je gehele vhost geven voor de ssl site? Mijn scanner zegt namelijk ook dat poort 443 gewoon functioneerd. Dus wlelicht is het een documentroot dat niet klopt waarbij vervolgens een 404 is opgegeven die niet bestaat en je daarom de errors krijgt. Tevens zou ik graag de server error.log zien, de error.log van de ssl-vhost. CustomLog logs/ssl_request_log En eventueel volgende optie aanzetten:

#SSLLog logs/ssl_engine_log
#SSLLogLevel info

Origineel geplaatst door Deimos
Kan je nog eens je gehele vhost geven voor de ssl site? Mijn scanner zegt namelijk ook dat poort 443 gewoon functioneerd. Dus wlelicht is het een documentroot dat niet klopt waarbij vervolgens een 404 is opgegeven die niet bestaat en je daarom de errors krijgt. Tevens zou ik graag de server error.log zien, de error.log van de ssl-vhost. CustomLog logs/ssl_request_log En eventueel volgende optie aanzetten:

#SSLLog logs/ssl_engine_log
#SSLLogLevel info

De config files staan hier
http://adslnetwerk.com/conf
Zo werkt die op localhost en op het interne IP nummer

En de error logs?