Many Windows internal tools are probably tied to Edge (or IE) so it might be a recovery action when some tool screams "I need IE! Help!" and the OS reinstalls the browser to accommodate this behavior.
Yes, this kind of OS self healing was introduced in Windows 2000, as fix to those applications that kept installing into C:\windows\system32, instead of actually configure the PATH and registry to locate their DLLs and COM.
I think it was ffmpeg developer who pointed out the inherent problem with this: quantity. 30 days to fix one vuln seems like reasonable when you are a billion dollar corp with thousands of pairs of hands and another thousand AI agents to throw at the problem but when you are that one developer from Nebraska thanklessly maintaining critical infrastructure (for free) it's not a matter of if but when will that burnout hits and your critical software is now a fart in the wind up for grabs for anyone willing to take up the charge.
They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure.
I know this sounds harsh but it really would be better for the world if these "processing complex untrusted data structures in C" enthusiasts found another hobby.
> They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure
Typically it's presented as-is and without any form of warranty, but in the hope it will be useful - not "suitable for critical infrastructure".
Perhaps those using it for "critical infrastructure" can write their own utilities, or chip in to support the developer whose hard work they apparently rely so heavily on, so bug fixes aren't done merely in the dev's unpaid time-off?
"Critical infrastructure" wasn't my phrase and I agree that the corporations who are using open source have a moral and pragmatic obligation to fund its maintenance.
But what does a developer (open source or not) who releases a container format parser and codec collection upon the world expect people to do with it if not run it on malicious data on personal devices?
> But what does a developer who releases [...] upon the world expect people to do with it
Sometimes you build things to explore how they work, or to test your assumptions about how something would work. To build your own knowledge about a format, language, or system. Hell, sometimes it's just the middle of a venn diagram between fun and practice.
And, because it's easy to throw something up on GitHub, you can say "Look at this cool thing I made", "Look, I actually can do what I claim on my resume", or "Anyone struggling in the same place as me can use this as an example workaround, or inspiration for a solution"
Nobody has to, or is even necessarily expected, to use it. Sometimes it's just the author sharing this cool thing they made.
True but C never went out of its way to highlight memory safety features and shut down (with a rather aggressive posture to boot) any criticism of the language with arguments revolving around this feature as if it was the Christ's second coming.
In lieu of finding out that there are in fact multiple memory issues in std is at least amusing and some might say well deserved egg in the face of the more, shall we say, enthusiastic defenders of the language.
Indeed though only those who taut the "memory safety" line as a mantra and some kind of catchall counterargument to any and all discussion that even remotely speaks ill of their favorite tool. Fanatics as you so aptly put.
I have my share of criticism of Rust. But even a safe language has to deal with unsafe memory etc. at some point in the stack. The goal is to minimize such uses of unsafe and for the cases of unsafe that exist to prove that they are safe.
These haha gotcha's are criticism leveled at language designers who never denied that there is unsafe code, that there can be bugs in unsafe code, and that such bugs can leak to safe code.
egg in the face
Is it an egg in the face when it requires LLM analysis to find these nowadays? It tells me that the Rust developers got really good at eliminating memory bugs that are lurking in unsafe code.
Also, this doesn't change anything to the benefits of Rust's ownership model, which removes classes of bugs that are very common in C/C++, so the Rust advocates were still right.
(I'll leave my rants about Rust in a thread where it's more appropriate, but they are not about memory safety.)
I don't think they're denying anything. I think they're muddying the technologies. They're saying "we don't need the screenshot to know what's displayed on your screen". With ACR, you don't need screenshots because you know what the content is. My understanding is that ACR is basically a fingerprint of the screenshot.
GPL is notoriously frowned upon when it comes to adoption in commercial environment (to a point where GPL licensed software is not allowed to be included in any way whatsoever). In that light I could see this as an attempt of a poison pill to prevent commercialization of their code by means of this "stigma" that is attached to the license itself. So a commercial entity cannot create an asahi alternative (or attach pieces of it to their own product) and charge money for it due to their legal dep telling them big no just because GPL is involved.
I can see that. I've been part of a conversation where GPL is treated like the son of satan because it requires giving back and no one seems to agree on the scope or what the license actually demands. So legal goes apeshit and management shits bricks because they might have to share some code.
reply