3 ms·
I don't think distros are going to be fixing vulnerabilities in all their packages. Is that what you mean?
by robertlagrant 4y ago
I don't think distros are going to be fixing vulnerabilities in all their packages. Is that what you mean?
- cuu508 4y agoYes, that is what I mean.
- phkahler 4y agoThat's not really their job. For log4j they could update that package. Any app that breaks as a result needs to be fixed upstream anyway, and then the distro can rebuild that. Fixes like that do get through the process, but it's not specifically the distros job to fix it. These problems are all about dependencies, which fall to upstream to make managable. If your favorite app breaks all the time it's probably because the code base is a giant mess. Oh, and some of the mess comes from too many different licenses in use, which prevents tighter integration of source code.
- ticviking 4y agoThat is the entire value dynamic linking and a stable ABI and API provide me. The ability to seamlessly replace an updated dependency by restarting an application and loading the library. If I'm just going to completely rebuild the app and all of it's dependencies I may as well statically link them and get the unique optimizations we can do after link time by analyzing the resulting executable.
- cuu508 4y agoIt's up to the distro to define what their job is. As I said, I prefer distros that proactively patch security issues regardless of what upstream does :-)
- robertlagrant 4y agoPoint being a log4j issue would be downstream of the distro, not upstream.
- phkahler 4y agoThe fix was to remove a feature from the library. That's upstream. That would also break things relying on the feature, so those apps would need to be fixed. That's also upstream. In each case, upstream WILL have to fix it. It's up to the distro whether they want to do anything about it prior to upstream getting it done.
- robertlagrant 4y agoIt's not upstream of the distro.
- ElevenLathe 4y agoThere are two actions that need to be taken: 1) fix the bug in the vulnerable package (cut a new version) 2) make sure the new, bug-free version is actually in use 1 is the responsibility of upstream (though sometimes distros will do this too, and release it themselves while they try to upstream the patch). 2 has to be done by somebody for every application using the vulnerable package, either a) automatically (for example, by Debian releasing the new log4j version and all dependent applications picking it up at runtime) or b) individually (by each dependent project's upstream updating the dependency, cutting a new Flatpak or container image, and getting users to update it). a is much more pleasant than b, at least in the universe as currently constituted. We can imagine a world where b is mostly automated so it is about the same or less work, but we don't live in that world yet.