I hope that a solution in some sense does not need to send more than som checksums that failed if there is a debug enabled, sign kernel modules that not trusted (ie. self sign), notify the program that hi there is a other program trying read your program’s memory or provided some restrictions memory space that even with debug enable you can’t read that space.
Yes, this is because the average user is dumb and content with guzzling down whatever bullshit gets thrown at them. This is a big part of why we really do not want to see the masses shift to Linux - they’ll bring the cooperate interest and the enshitification they love.
I do agree that best solution is that we don’t need it.
Sadly bassed on what i hear, users are willing do Things on kernel level to cheat. Ie read/Write memory from a different program.
Youtube: Core dumped: can a gamer company really sabotage your PC? made a good video summarizing the issue.
I hope that a solution in some sense does not need to send more than som checksums that failed if there is a debug enabled, sign kernel modules that not trusted (ie. self sign), notify the program that hi there is a other program trying read your program’s memory or provided some restrictions memory space that even with debug enable you can’t read that space.
Yes, this is because the average user is dumb and content with guzzling down whatever bullshit gets thrown at them. This is a big part of why we really do not want to see the masses shift to Linux - they’ll bring the cooperate interest and the enshitification they love.