Daer opsi users
we have published opsi-configed 4.0.7.3.4 in testing:
http://download.uib.de/opsi4.0/testing/ ... 3.4-1.opsi
Hopefully, we solverd the problem that, only with some servers, the communication between the opsi-configed and opsiconfd broke with SSL handshare errors.
At the moment, the solution is to use a fallback option to the protocol version TLS v1 . To switch to it, you use either the property java_static or the the property tlsv1.
Additionally, there are some bug minor fixes, especially for the wake on lan functions.
Kind regards
Rupert Röder
Changelog
opsi-configed (4.0.7.3.4-1)
* additional request property connection close
* logging of SSL protocol
* in package additional property fallback_tlsv1
opsi-configed (4.0.7.3.3-1) STABLE; urgency=medium
* fixed missing call for WoL in scheduler
* fixed missing identification of configserver connection if its hostname differs from its opsi id
* fixed line endings of logfiles when exported as archive
* host_read method reimplemented for mysql present
opsi-configed (4.0.7.3.2-2) STABLE; urgency=medium
* new property: java1.7 static in product folder
New opsi 4.0.7-Paket opsi-configed in testing
New opsi 4.0.7-Paket opsi-configed in testing
opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.
Wondering who's using opsi? Have a look at the opsi map: http://opsi.org/opsi-map/.
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.
Wondering who's using opsi? Have a look at the opsi map: http://opsi.org/opsi-map/.