Re:Log4j 2.15.0 – Previously suggested mitigations may not b...
by tfigment on Thursday December 16, 2021 @08:34AM
(#29577917)
What i discovered was all of my applications that use log4j do not use version 2. They have out of date dependencies or use slf4j. I'm not sure how i feel but mostly happy im not scrambling. I wonder what adoption rate v2 actually has.
Re:Log4j 2.15.0 – Previously suggested mitigations may not b...
by yawaramin on Thursday December 16, 2021 @08:39AM
(#29577943)
I think adoption has mostly gone towards slf4j+logback now.
Re:Log4j 2.15.0 – Previously suggested mitigations may not b...
by mrclark411 on Thursday December 16, 2021 @12:35PM
(#29581018)
logback is *gpl, I think that scares folks away.
Re:Log4j 2.15.0 – Previously suggested mitigations may not b...
by gunnarmorling on Thursday December 16, 2021 @02:15PM
(#29582495)
Logback is dual-licensed under EPL v1.0 and the LGPL 2.1, as per the licensee's choosing [1]. In particular, it is not licensed under the GPL.
Re:Log4j 2.15.0 – Previously suggested mitigations may not b...
by yawaramin on Thursday December 16, 2021 @06:51PM
(#29585677)
It scares away people who see 'GPL' and refuse to read further, perhaps. Not only is it dual licensed, but both licenses (EPL and LGPL) freely allow linking with proprietary software.
It has been used by millions of developers for the better part of a decade before anyone disclosed the implications.