4 ms·
Speaking of disingenuous, since when is log4j “web 2.0”? > The claim that Web3 is rife with hacks, when you have daily hacks of Web2 (are we just ignoring Log4
by acdha 5y ago
Speaking of disingenuous, since when is log4j “web 2.0”?
> The claim that Web3 is rife with hacks, when you have daily hacks of Web2 (are we just ignoring Log4j, which is a huge deal and happened 2 days ago)
That’s also worth thinking less shallowly about for a second reason: if a cryptocurrency service, wallet, etc. you used was hacked due to log4j, you’d lose everything without recourse. This is not true of the mature banking system, and it might be useful to consider how many people would consider that a requirement.
- sneak 5y ago"web 2.0" = centralized web application servers providing usually-json API backends for javascript clientside applications running in a browser. Usually written in Python, Ruby, Java, or PHP. Sometimes written in Perl or Go or Rust. Clicks are not usually full pageloads (that is, SPAs). Many (maybe even most?) of those web 2.0 applications are written in Java and those that are, almost all of them use log4j. (web1 was serverside rendering of html, sending down complete html pages for each user interaction.)
- acdha 5y agoI’m quite familiar with web 1 & 2’s meaning having worked on both so while I’d want to fix that definition it’s really distracting from the main point: log4j has nothing to do with either, as evidenced by the many projects which didn’t even use Java. It’s just a library, and compiling into byte code for some blockchain VM wouldn’t make it a cryptocurrency library, either.
- ahtihn 5y agoWeb 2.0 predates SPAs and has basically nothing to do with that. Web 2.0 is basically websites with user generated content. See https://en.m.wikipedia.org/wiki/Web_2.0 https://en.m.wikipedia.org/wiki/Web_2.0 and most other sources you find when googling "what is web 2.0" And by the way, a significant number of java backends don't use log4j2 as a logging backend (the vulnerable part).
- dvt 5y ago> Speaking of disingenuous, since when is log4j “web 2.0”? Let's assume Web 2.0 is 2008 to the present day. Every single big corp I worked at during that time was a Java shop (serving via Tomcat/Jetty), and log4j is ubiquitous in every Java shop. Minecraft (a gaming epitome of Web 2.0), basically blew up because of Log4j.
- ahtihn 5y agoSorry but log4j is not ubiquitous. Slf4j with logback has a significant presence. Spring boot doesn't come with log4j backend by default.
- acdha 5y agoSo your definition of “web 2.0” includes every programming language and library used to build web 1 or 2 apps, along with all kinds of other things? That’s quite the stretch — and it’s telling that you’re only using that as a negative to attack things which you don’t have a personal financial stake in. I don’t imagine you’d like it if every vulnerability in some library used by a blockchain-related project was billed as a cryptocurrency problem.
- dvt 5y agoSorry, but I think you're arguing from such bad faith, not sure if this conversation is redeemable. Imo, Log4j is as part of web2 as technologies like MongoDb or AJAX/XMLHttpRequest. Arguing the opposite is just completely nuts. I mean, Play Framework (a staple of Web 2.0 Java & Scala), uses Log4j implicitly[1]. Have you written any Web2 apps in Java? It doesn't seem like you have. > The Play logger is built on Log4j. Since most Java libraries use Log4j or a wrapper able to use Log4j as a backend, you can easily configure logging that is well-suited to your application. [1] https://www.playframework.com/documentation/1.2.x/logs https://www.playframework.com/documentation/1.2.x/logs
- acdha 5y ago> I think you're arguing from such bad faith, not sure if this conversation is redeemable. Please tell me this is a joke. You compared two unlike things, and now it’s “bad faith” when you can’t support the claim? > Log4j is as part of web2 as technologies like MongoDb or AJAX/XMLHttpRequest This is half right. As with log4j you can tell what things are “web 2.0” by asking whether you had to use them or not. People built many, many Web 2.0 sites without Mongo or Java but they had to use XHR because that’s what web browsers supported — until Fetch arrived later, there wasn’t a good alternative. Someone using your site didn’t know what you used server side but they definitely could tell what your client-side code (which is what made it Web 2.0 instead of 1) was doing.