| Christian Herzog wrote: |
|
[...] we're evaluating elog right now at the Physics Department of ETH Zurich and I'm trying to come up with a good config. One of the first steps of course was to enable SSL/https. With http, all tested browsers work fine, but with https at least Google Chrome 16 and IE 9 do not get past the "unknown certificate" warning and I see "TCP connection broken" errors in the log file. Firefox however works fine. Same behavior on Linux, Mac and Windows (given the browser in question is available). elog server is running on Lucid.[...]
|
 ⇄
Detect language » English
If you want to use https you should know what a certificate is.
Certificates are used to encript the data, but at the same time they are used to identify the host.
ELOG is delivered with a self generated certificate.
This can be used to encript the data, but no certification authority knows this certificate, so nobody can guaratee that you are connected to the right host.
Most browsers will warn you, that nobody did and if you don't care you need to change the security settings of you browser to accept the connection anyway.
The proper way out of this is to buy a certificate from a certification authority. Or to switch off https. (See https://midas.psi.ch/elog/config.html#global SSL option) |