News for hackers. Stuff that matters.
Re:Log4j: Between a rock and a hard place by dexwiz on Saturday December 11, 2021 @03:20PM (#29523926)
The last part advises to be feature conservative to avoid promises all together. For that look to enterprise software where backwards compatibility is a legal agreement. This carries a bunch of alternative issues.
Re:Log4j: Between a rock and a hard place by floatboth on Saturday December 11, 2021 @03:43PM (#29524104)
"Features" is a way too abstract thing to blame, tbh.

The elephant in the room here is the excessive dynamism allowed by default on the JVM platform. How many applications actually need fancy classloaders? Why isn't every step to get there - "loading a class from anywhere that isn't my JARs", JNDI, JNDI's LDAP backend, etc. - an explicit opt-in flag to the VM? Java's wide-open defaults are what made the blast radius of this huge.

Re:Log4j: Between a rock and a hard place by zmmmmm on Saturday December 11, 2021 @04:06PM (#29524310)
Java's dynamic classloaders were one of it's original tantalising features. That you could have code from one place running somewhere else - "agents" could literally send their bytes to a device to execute there, run there and then erase themselves when they were done. It sounds crazy these days but it was all meant to be held together by the security model - built in at the core it was safe to let foreign byte code execute locally because the completely managed VM could enforce a security sandbox that allowed the code to do only exactly what it was meant to.

In some ways that is where this and all those features fell down ... if log4j had constrained those classes within a security sandbox it wouldn't matter what they did. But nobody understands or uses Java security permissions. The whole system is byzantine and drives people crazy whenever they do run into it. But if it had worked you could be asking the question, "why did log4j allow the permission for the remote code to do bad things" rather than "why was remote code allowed to execute".

Re:Log4j: Between a rock and a hard place by krzyk on Saturday December 11, 2021 @03:51PM (#29524178)
There are popular languages that have `eval()`, so I don't see why blame Java only?
Re:Log4j: Between a rock and a hard place by jpfed on Saturday December 11, 2021 @05:38PM (#29524919)
Don't get us wrong, eval() is terrible too.
Re:Log4j: Between a rock and a hard place by dvhh on Sunday December 12, 2021 @09:15AM (#29529780)
Meaning that Log4J is certainly not the only library to have the problem, maybe the one with the larger footprint, what about JSP ?
[dead]
Re:Log4j: Between a rock and a hard place by PufPufPuf on Saturday December 11, 2021 @03:46PM (#29524123)
The original is understandable. The person might not be a native speaker and calling their grammar "questionable" is too harsh, especially on an online forum. Also I don't think some of your "fixes" are necessary or meaningful.
[dead]
Re:Log4j: Between a rock and a hard place by Talanes on Saturday December 11, 2021 @06:49PM (#29525448)
Using semicolons to join sentences together isn't a super common style of writing for online comment sections. If you are unable to read a paragraph composed of shorter, more discrete sentences, that's on you.
Re:Log4j: Between a rock and a hard place by scubbo on Saturday December 11, 2021 @07:35PM (#29525801)
> I attempted to fix your questionable grammar as[sic] to make your writing easier to understand

Muphry's Law strikes again! I think you meant "...so as to make..."

(+1 to the other reply - the original was perfectly readable)

Re:Log4j: Between a rock and a hard place by eatYourFood on Saturday December 11, 2021 @08:12PM (#29526081)
Ideally you’d just remove the word ‘as’ for the most concise and correct sentence.