|Re: [orbit-dev] [cross-project-issues-dev] log4j vulnerability in Eclipse: update to 2.16.0?|
On Sat, Dec 11, 2021 at 8:36 PM Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
On Sat, Dec 11, 2021 at 11:35 AM Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
On Dec 11, 2021, at 10:16, Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:It would be great to learn vulnerability clean-up process with Eclipse Orbit team to then apply it to Eclipse Passage.
There is no Orbit team. Orbit is driven by project committers using/needing libraries in Orbit.I encourage the Eclipse Passage project to submit a Gerrit review for a newer version.
considering the buzz around this vulnerability I went ahead and pushed an update to log4j 2.15 for orbitnote that the required clearlydefined score isn't reached yet, if this doesn't change soonmaybe someone can contribute the missing information to clearlydefined orwe file CQs to get the license approval for the new version
since the log4j project published another release 2.16.0 adding more fixes for CVE-2021-44228I pushed another update for Orbit:and contributed curations to the corresponding clearlydefined entries_______________________________________________You can also try a new way as described by Mickael here:
orbit-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev
Back to the top