Hi Kuksa Community,
I assume you all have heard about the recent discussions on the log4j vulnerability. We are currently checking the repositories of Eclipse Kuksa whether they are affected and identified
https://github.com/eclipse/kuksa.integration
as a candidate repository, which at least references this dependency. As this repository is used for internal integration testing there should be no direct effect on users. However, we now would
like to take this opportunity to start a discussion on how to further proceed with this repository. As the integration tests rely on technology (Jenkins, remote clusters) not used in other repositories of the project such as kuksa.val, we would suggest to
archive the integration test repository (https://github.com/eclipse/kuksa.integration) and incrementally migrate the tests to their respective repositories if sensible.
We started this discussion on the issue tracker
https://github.com/eclipse/kuksa.integration/issues/36
WDYT?
Kind regards,
Johannes
Mit freundlichen Grüßen / Best regards
Dr. Johannes Kristan
Product Area IoT Platform Open Source (IOC/PAP-ESC-OS)
Bosch.IO GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch.io
Tel. +49 30 726112-432 | Mobil +49 172 4974659 | Telefax +49 30 726112-100 | Threema / Threema
Work: AMRKF8N8 | Johannes.Kristan@xxxxxxxx
Registered Office: Berlin, Registration Court: Amtsgericht Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Dr.-Ing. Thorsten Lücke; Managing Directors: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne Reckling