16 karma · joined April 3, 2024
Break: interrupt (a sequence, course, or continuous state). "this broke the pattern of generations remaining in the place where they were born"
Innovative: (of a product, idea, etc.) featuring new methods; advanced and original. "innovative designs
Ever modified a product to implement a new original advanced method that didn't interrupt a single existing mechanism or structure?
If so, I wish I had your codebase!
Refer to your own link.
The author misses that the buildtime magic for the xz exploit is not in the m4 file but in an obfuscated, compressed, encrypted, binary disguised as a test file that alters the build process at multiple stages (configure and build)
A better argument can be made that the act of compiling a binary / obfuscating / minifying code instead of interpreting code directly is the fault.
If the software were to explicitly depend on <vulnerable library> and moving to <patched library> broke it that would be the nail in the coffin for me / make me question whether I want to spend the effort maintaining the project.
This is an architectural problem not an OS constraint.
And they're completely correct to abandon this software in my honest opinion as the developers already have.
If you need this run a 32bit VM under the 64bit OS so the virtualised CPUs can handle the 16bit application.
The author would genuinely benefit from redhats decade long support models provided his desired tooling works on Linux.
The real concerns are in the SaaS / Remote Resource / Online Activation Space.
eg software that won't wake up if it can't call home, software that has reduced or no functionality if it can't stream remote data, "apps" that are just webkits loading a pre-set url for a completely online service.