08-May-2017

Webserver update
Just updated WASD but there is a problem with the secured access, so webmail and operator sites are not accessible; Weird is that doesn’t ask for authentication – it just fails to show completely – nothing is returned… Problem is that the WATCH output cannot be created – because the admin tools live in the (no inaccessible) operation site….
Reason: from the release notes:

TLS/SSL default configuration (cipher list and options) maximises security and is compatible with most modern agents (minimum Firefox 27, Chrome 30, IE 11 on Windows 7, Edge, Opera 17, Safari 9, Android 5.0, and Java 8). Ciphers require “Forward Secrecy” and presence of [LOCAL]DH_PARAM_nnnn.PEM safe prime files. To support older clients the configuration must be downgraded

So there is some reading and postprocessing to do.
By the way: the configuration files that were created in version 8.something, has never been updated, so it’s a good moment to do it now, using the example file.
In the mean time, I have reversed the installation, so I’m back on 10.0.2, until it’s clear what to do..

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.