News for hackers. Stuff that matters.
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by johnklos on Friday July 19, 2024 @02:34PM (#41009626)
It's a nice idea, but has that worked historically? Some people will make changes, but I think we'd be naive to think that things will change in any large and meaningful way.

Having another I-told-you-so isn't so bad, though - it does give us IT people a little more latitude when we tell people that buying the insecurity fix du jour increases work and adds more problems than it addresses.

Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by __MatrixMan__ on Friday July 19, 2024 @02:44PM (#41009713)
Sure, on long enough timescales. I mean, there's less lead in the environment than there used to be. We don't practice blood letting anymore. Things change. Eventually enough will be enough and we'll start using systems that are transparent about what their inputs are and have a way of operating in cases where the user disables one of those inputs because it's causing problems (e.g. crowdstrike updates).

I'd just like it to be soon because I'm interested in building such systems and I'd rather be paid to do so instead of doing it on my off time.

Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by Bluestein on Friday July 19, 2024 @03:22PM (#41010118)
> We don't practice blood letting anymore. Things change

Gonna make me a Tshirt outta this :)