News for hackers. Stuff that matters.
Re:“Open source” is broken by wyldfire on Saturday December 11, 2021 @03:00PM (#29523755)
> I simply do not want to be in a situation where my software that I develop as a passion project on the side is holding people's companies together.

People love to hate on Richard Stallman but he was really clear about the motivation for Free Software (which is not the same as Open Source but shares some tenets).

What companies do with the source is their thing. They get all of the benefits and all of the responsibilities. But the beautiful thing is that if that maintainer is dead or missing or no longer interested, you CAN fix it. Which is very difficult / nigh impossible for closed source.

Re:“Open source” is broken by jobigoud on Saturday December 11, 2021 @03:49PM (#29524158)
> What companies do with the source is their thing. They get all of the benefits and all of the responsibilities.

I know this very well and for some irrational reason it still makes me anxious to think about the many people relying on one of my free-time project that is used in classroom and medical settings. When there is a nasty bug found it's hard to shake the feeling of responsibility.

I have disabled the counting of downloads for this reason, I would rather not know just how many people rely on it and instead focus on improving it without pressure.

Re:“Open source” is broken by phkahler on Saturday December 11, 2021 @05:19PM (#29524779)
>> When there is a nasty bug found it's hard to shake the feeling of responsibility.

I know right? Someone just opened a github issue for a CVE in one of our dependencies. It's only relevant if you're opening a .DXF file from an untrusted source, so it doesn't seem terribly relevant but yet... And updating to a newer version would take effort, and we want to replace it with something else anyway which would take effort. None of that effort is where I want to spend my free time. But I do work on the software because I like it and really want it to continue being around and useful, and that isn't going to happen unless I (and others) make it happen.

Re:“Open source” is broken by c-smile on Saturday December 11, 2021 @05:35PM (#29524894)
> Which is very difficult / nigh impossible for closed source.

Closed source does not mean that the customer has no access to it.

In case of my Sciter, for example, customers are getting access to SVN server with sources. Some of them are sending patches with fixes and features.

Sciter's [1] core customers are antivirus vendors - highly professional, dedicated and disciplined teams that know very well what they are doing.

It is not an open source but not a closed source either. Rather a professional club where members value each other time and efforts.

[1] https://sciter.com

Re:“Open source” is broken by bsedlm on Saturday December 11, 2021 @07:20PM (#29525665)
similarly, free software (in RMS's sense) does not mean you cannot charge for it. however this has practical considerations which are still open problems
Re:“Open source” is broken by koonsolo on Saturday December 11, 2021 @06:08PM (#29525156)
Same for the Unreal Engine
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @03:07PM (#29523817)
Except you can't because hundreds of thousands of project have "log4j" in their dependency list not "wyldfire-fixed-log4j". If log4j broke and there was no maintainer, a fork would not fix things.
Re:“Open source” is broken by IiydAbITMvJkqKf on Saturday December 11, 2021 @03:23PM (#29523953)
Sure you can fix it, change the "log4j" in your dependency list to "wyldfire-fixed-log4j". You can't do that with closed source (either because you care about legalities, or because you have no way of obtaining a compilable and readable source code).
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @03:35PM (#29524039)
Until all hundreds of thousands of projects have changed that, it'll take time.

That doesn't mention the fact you now also have to fork unmaintained projects relying on log4j to use the new version. If you're developing a major java projects, that's potentially thousands of dependencies you have to patch.

I'm not suggesting that closed source is the solution, I'm saying the current system is not sustainable and neither is just forking projects. Because which fork do you follow, and how do you make sure all your dependencies follow the fork you want and not an unmaintained fork?

Re:“Open source” is broken by the_duke on Saturday December 11, 2021 @03:42PM (#29524099)
Some package managers (eg yarn , cargo) have a solution for that and allow you to specify a local resolution override that will apply to all dependencies.
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @03:45PM (#29524114)
But again, that means EVERY single product, open source or not, will have to patch their deployment to use the fork instead of simply using the updated version of upstream. Permanently no less if it's unmaintained.

Meaning every single Java product would have to include that "if you want to use log4j, you have to include this patch line to use a fork, because of unmaintained dependencies".

That just ossifies log4j and fixes nothing. Patching dependencies in Cargo is not meant to permanently replace code, it's to be used while you're waiting for an upstream merge.

Re:“Open source” is broken by IiydAbITMvJkqKf on Saturday December 11, 2021 @04:00PM (#29524257)
You can fix it for your own applications and libraries. The tooling exists.

You can't force other people to use your fork.

Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @04:06PM (#29524305)
Correct, all those other people will have to manually find some fork or make their own, repeating the same work thousands of times and ossifying that some part of your java build system now permanently includes a section to patch log4j dependencies.
Re:“Open source” is broken by alexvoda on Saturday December 11, 2021 @07:47PM (#29525907)
You can not force your dependencies to do what you want. You can only patch the problem for yourself and maintain that patch in the build system, or you can fork each dependency in the chain, maintain those and then your build system is cleaner.

There is nothing wrong with these options.

Re:“Open source” is broken by zaarn on Sunday December 12, 2021 @03:39AM (#29528060)
Forking yourself is not scalable for fixing a 10/10CVE and I don't get how people think that somehow "fork it" is a viable solution across the entire industry.

This is not about forcing my dependencies to do anything, this is about caring about maintainers and maybe ensuring that the bedrock of our ecosystems aren't maintained by unpaid volunteers in their free time, exploiting the sweat on their backs for our amusement for free. Forking the project is just spitting on their efforts on top of that.

Re:“Open source” is broken by alexvoda on Wednesday December 15, 2021 @03:14PM (#29571046)
Entirely agree, we should find ways to reliably support upstream. But that is a different issue, and unfortunately it is one that the main beneficiaries are not willing to solve.

Forking solves the issue of an upstream dependency not willing to fix a bug.

Re:“Open source” is broken by zaarn on Wednesday December 15, 2021 @11:16PM (#29574769)
As I've pointed out a few times now, forking upstream is not a long term or sustainable solution.
Re:“Open source” is broken by kristjansson on Saturday December 11, 2021 @04:12PM (#29524350)
Does it matter that other products don’t patch something that yours does? Like, sure, it’s unsatisfying from an ecosystem perspective, and one would hope for fixes to be incorporated upstream. But if they aren’t, who cares if other products are broken after you’ve patched the ones you’re responsible for?
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @04:14PM (#29524360)
It does because now I pull in a dependency that indirectly relies on log4j instead of my favorite fork of log4j and I end up having the same CVE in the project anyway. Yes this needs to work ecosystem wide, otherwise you have fixed nothing at all.
Re:“Open source” is broken by the_af on Saturday December 11, 2021 @05:09PM (#29524719)
> It does because now I pull in a dependency

How would proprietary software make this better? You wouldn't even have anything to pull in!

Is your argument "having the source code and the legal rights to fix this bug even when nobody else wants to or even can fix it is not good enough because not everyone will use my fix"? Because good luck with proprietary software then!

Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @06:21PM (#29525269)
My argument is not closed source. My argument is that "just fork it" does not magically fix all problems. Closed source makes this worse but "fork it" is no answer either.

I believe I made this very clear on my very first comment.

Re:“Open source” is broken by kristjansson on Saturday December 11, 2021 @07:28PM (#29525734)
Right … open source doesn’t guarantee an absence of problems, only that, in the worst case, a user can repair a problem herself. As you note, that’s strictly preferable to closed source, where a problem with a dependency is not guaranteed to be fixable by the user. Isn’t that enough?
Re:“Open source” is broken by zaarn on Sunday December 12, 2021 @03:41AM (#29528062)
That is not sufficient no. As a user, I want to be able to support developers so they have the time to fix things that go wrong. That the log4j Maintainers are entirely unpaid for maintaining what amounts to the bedrock of the java ecosystem is a tragedy and that people continue to argue that this is how it should be are simply exploiting what amounts to slave labor.
Re:“Open source” is broken by the_af on Sunday December 12, 2021 @05:59AM (#29528625)
> As a user, I want to be able to support developers so they have the time to fix things that go wrong.

As an individual user, you shouldn't be required to. It's not how or why the project started, anyway. Maybe big companies whose system depend on log4j could fund it, yes.

> what amounts to slave labor

That kind of hyperbole doesn't help the discussion. The situation is nothing at all like slave labor.

Re:“Open source” is broken by IiydAbITMvJkqKf on Sunday December 12, 2021 @06:09AM (#29528671)
You have zero clue about what slave labour is.
Re:“Open source” is broken by zaarn on Sunday December 12, 2021 @06:13AM (#29528691)
I have plenty of clues of what slave labor is and big companies exploiting the hard work of people working for free without paying them is definitely pretty damn close.
Re:“Open source” is broken by IiydAbITMvJkqKf on Sunday December 12, 2021 @07:55AM (#29529208)
This is reddit tier derangedness, any one of the millions of people living under real slavery, where you get lined up to a wall and shot if you refuse to work would gladly switch places with anyone living under what you dream up to be "slavery".
Re:“Open source” is broken by the_af on Sunday December 12, 2021 @08:53AM (#29529606)
Agreed, calling this slavery is a level of hyperbole that doesn't help the debate at all.
Re:“Open source” is broken by the_af on Saturday December 11, 2021 @08:45PM (#29526274)
I misunderstood you then. I agree with your statement. Open source doesn't solve all problems, just some. There are hard problems about dependency management and vulnerabilities that are not magically solved by something being open source, I agree.
Re:“Open source” is broken by kube-system on Saturday December 11, 2021 @06:45PM (#29525429)
The problem is, my dependencies also have dependencies. If the problematic dependency is any more than one degree of separation removed, you're back to square one.
Re:“Open source” is broken by debug-desperado on Saturday December 11, 2021 @10:09PM (#29526778)
A nightmare in Node world perhaps (our latest simple web server has over 2,000 dependencies).

In the Java world it’s much simpler with a few excludes in your POM. Especially for libraries that keep stable interfaces, such as a logging library.

Re:“Open source” is broken by zaarn on Sunday December 12, 2021 @03:41AM (#29528065)
How many excludes is Java going to ship is forking the problem of unmaintained libraries away becomes too much? When it reaches 5kb? 10kb? 100kb of excludes?
Re:“Open source” is broken by blindmute on Saturday December 11, 2021 @03:53PM (#29524198)
Code doesn't just "break". It still works the same. If a vulnerability is discovered you either update the package or switch to a fork. Switching is not really that much extra work compared to updating. This issue has really nothing to do with open source except that you have the extra option of forking.
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @04:04PM (#29524286)
I argue that if your code gets assigned a 10/10 Severity CVE, then it broke, even if nothing changed. It just broke a while ago.

Switching one library is not much work. But if it becomes the standard approach then the first time you fire up your java project you either spent 30 minutes to put in all the exclusions to provide your favorite forks of dead projects or your pom.xml will already be 5KB large on generation just for those exclusions and patches.

Re:“Open source” is broken by jacoblambda on Saturday December 11, 2021 @03:33PM (#29524028)
Strictly speaking in the Java space that's a perfectly reasonable assumption. It's a bit more work but you can just substitute the jar/modules for log4j following the build with the patched versions.

At the end of the day it is just a bunch of class files in jars/zips which makes patching a lot easier.

Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @03:37PM (#29524053)
Hot patching a jar is not a scalable solution in the long term, especially if you're considering that in a larger project there may be multiple unmaintained projects that now need permanent hotpatching.
Re:“Open source” is broken by ecnahc515 on Saturday December 11, 2021 @03:46PM (#29524126)
As others mentioned, for any companies relying on this software, that's their problem, and it's nothing more funding and resourcing can't solve.
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @04:05PM (#29524300)
This isn't only about companies, people who develop open source software on their own are just as affected by log4j. Funding and resourcing can at least help people and maybe incentive handing the project to someone else.
Re:“Open source” is broken by jacoblambda on Saturday December 11, 2021 @03:44PM (#29524109)
At least with gradle you can easily add some logic to the buildscript to substitute all instances of a specific dependency for a java library/application with a fork.

It's only a handful of lines of code and it is technically a bit hacky but it's really no worse than any of the other jank you are forced to do when building any moderate to complex gradle based java project.

Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @04:04PM (#29524292)
And when another library is unmaintained and breaks, you add those few lines again. And again and again and again, until your gradle file is 90% hotpatching your dependencies.
Re:“Open source” is broken by jacoblambda on Saturday December 11, 2021 @04:35PM (#29524494)
Yep but that's just the breaks. Especially with ecosystems that have tall dependency trees.

Luckily those few lines can mostly be shared and you end up with a handful of lines and a map from old dep to new dep which makes it not too painful.

This whole issue is why I don't like these ecosystems but at the very least in the Java space dealing with this issue isn't too painful. I can't speak for the JS space but this is also a pretty trivial fix in the Rust space and it isn't too painful with C++ or C projects. Nix (mostly used for Haskell but it's a pretty solid universal package manager) has some pretty good tooling for modifying upstream dependencies. Spack (package manager specialised for HPC and embedded projects) has really good support for this as well.

My point being that people have run into these issues in the past a lot in certain spaces and as a result those spaces have come up with solutions for this problem a long time ago. It just so happens that for the most part the average dev doesn't see a lot of that because these issues get dealt with upstream or just aren't common in most industries. The embedded industry is particularly used to this considering how much of the kit from manufacturers is just outright wrong or broken 3 levels deep. The only reason I'm as well versed with this as I am is because I've been in the embedded space patching over broken HALs and I've bled my blood dealing with legacy enterprise applications that were initially written in Java 1.1 and haphazardly dragged along over the decades.

TLDR: This is an ugly fix but ultimately it's the best ugly fix to an ugly problem and every software ecosystem eventually gets to deal with it once they get old and crusty enough.

Re:“Open source” is broken by dopkew on Saturday December 11, 2021 @07:41PM (#29525858)
Off-topic but very important: The widespread misuse of the word 'dependency' is very very icky, linguistically speaking. This word originally meant: 'in a state of being dependent'. Usage: "Ronny hated his dependency on the kindness of strangers.". But it's being used to refer to the 'dependent', as well as the 'dependee', which is very poor form:

https://english.stackexchange.com/questions/25575/what-is-th...

https://wikidiff.com/dependee/dependent

Re:“Open source” is broken by pritambaral on Sunday December 12, 2021 @04:29AM (#29528241)
The original meaning still works. In the software world, where abstractions abound, each dependee of yours can be said to add one 'state of being dependent' to your set of requirements. That's what it meant originally in this young field; when an author chooses to use a library instead of writing their own code, they're adding a requirement for the user ("Hey, you gotta have this thing already installed"). The software is in a state of being dependent on each of its dependees, individually. Each such state could be removed by replacing the library, and thus there'd exist one less 'dependency'.

----

Yes, this is mental gymnastics, another fine staple of this glorious field.

Re:“Open source” is broken by zaarn on Sunday December 12, 2021 @03:43AM (#29528069)
I don't think that is any issue whatsoever, the software engineering world has largely agreed on the usage of the word dependency, doesn't really matter what linguists think. Language is consensus, not thesis papers.
Re:“Open source” is broken by quickthrower2 on Saturday December 11, 2021 @03:55PM (#29524217)
Thats the problem. If you use say React then you are using it as is without any warranty implied. React is the equivalent of an aircraft in complexity when looking at its dependencies and then the browser stack itself on top!

React gives you a free copy of an aircraft and will probably maintain it for years. But maybe they rely on an altimeter developed by a poor person who decides they dont have time to work on it because they need to help their mum.

Well thats everyone elses problem now.

but the ease of download and use of React and other code libraries creates a sense of entitlement.

Yes if its broke and you need it fixed you have to pay someone now!

Its still libre its just not gratis anymore

Re:“Open source” is broken by mantaraygun on Saturday December 11, 2021 @03:17PM (#29523895)
> hundreds of thousands of project have "log4j" in their dependency list

That's on them. They can migrate to wyldfire-fixed-log4j if they want, or to whatever other fork they want, or they can keep using the old busted shit. It's up to them, there's no problem here.

Re:“Open source” is broken by blibble on Saturday December 11, 2021 @03:48PM (#29524143)
the documentation also needs to include the 5 line dependency exclusion that you place in your pom to exclude the bad version
Re:“Open source” is broken by zaarn on Saturday December 11, 2021 @03:59PM (#29524244)
And if you do that everytime an unmaintained project gets a 10 severity CVE, we'll have that at 200 lines in no time. Proabably petition whatever generates your Pom.xml to auto-include those lines.
Re:“Open source” is broken by 0xdeadb00f on Sunday December 12, 2021 @08:32PM (#29535578)
> What companies do with the source is their thing.

I think RMS and the GPL would disagree with that statement.

[dead]
Re:“Open source” is broken by unethical_ban on Saturday December 11, 2021 @03:22PM (#29523942)
I don't know if you're a troll, or if you really managed to stuff three different far-right rhetorical tropes into one sentence in order to declare the cooperative development of software as immoral, because megacorps can't force people to pay for something.