SAP's Response to Apache Log4j

There says: "SAP continues to investigate the remote code execution vulnerability related to Apache Log4j disclosed on Dec 10, 2021. SAP encourages our customers to update to the latest version of Log4j, where applicable." So far, so good. Then the reader finds a list of SAP applications that are not affected, affected, maybe affected.

Now a reasonable comment from the editor-in-chief of E-3 magazine should follow, and possibly a trade-off between Java and Abap. However, it can be assumed that E-3 readers have also been sufficiently informed via other channels in the past few days - and what seems even more important, with the comment of Kristian Köhntopp from Heise-Verlag in Hannover, the text that concludes everything has already been written, and there is nothing more to add. This text was brought to my attention by my friend Hinrich Mielke from Adesso Orange - a big thank you for that. And the undivided admiration goes to Kristian Köhntopp, of whom the Heise website says: "Kristian Köhntopp started programming in 1983 and has been online since 1988. Since then he has done various things with computers of all kinds, but in view of the situation is thinking about a career as a landscape gardener.

Here's the latest information: the DSAG Technology Days have been moved from February 22 and 23 to May 3 and 4, 2022, but will remain in Düsseldorf. A keynote by Kristian Köhntopp at the DSAG Technology Days would be very helpful educational work for the SAP community, wouldn't it?