[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Log4j 1.x vulnerability
|
Dirk,
Thanks. That's really great! It would be great for this release
cycle if it were jar signed and available from Orbit so that we
could ship it with 2022-03...
There are people who are concerned:
https://www.eclipse.org/forums/index.php/mv/msg/1109656/1849775/#msg_1849775
Though I'm not sure if they would consider the problem being
fixed in 1.2.19 a fact and even if its a fact if it would be a
fact that matters...
Regards,
Ed
On 08.02.2022 15:48, Dirk Fauth via
cross-project-issues-dev wrote:
Hi,
I got in contact with the reload4j team. They
changed the Bundle-SymbolicName to org.apache.log4j and fixed
several OSGi meta data related issues in the meanwhile. Today
they published 1.2.19 which should work as a drop-in
replacement in Eclipse based applications where Require-Bundle
was used. My local tests worked so far.
That said, re-bundling for Orbit should not be
necessary as reload4j could directly be consumed via Maven
Central.
Just wanted to keep you updated.
Greez,
Dirk
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev