The issue is solved, Jeff also has taken a look and explained the process a bit
more.
In the apache SSL configuration there are two options that need to be disabled,
SSLSessionCache and SSLSessionTickets.
SSLSessionCache none
#<IfModule mod_socache_dbm.c>
#SSLSessionCache dbm:/var/lib/apache2/ssl_scache
#</IfModule>
#<IfModule mod_socache_shmcb.c>
#SSLSessionCache shmcb:/var/lib/apache2/ssl_scache(512000)
#</IfModule>
#SSLSessionCacheTimeout 300
SSLSessionTickets off
SSLSessionCache is normally enabled, through the mod_socache_shmcb module. I
have set SSLSessionCache to off. Even tough there are no PSK ciphers enabled,
and I expected PSK would not be in use, it looks like the cache caused the
problem. As Jeff explained, probably the initial session is started and creates
a cache entry, when a resume/reuse is done it will go through the PSK module to
match the cached entry. And then it fails. So by making sure there is no cache
the connection doesn't give an error.
Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
Flight Forum 3000 5657 EW Eindhoven
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
