![]() I would think WASM (coupled with a minimal runtime like Wasmer) might provide a means to deal with this issue by signing the packaged sandbox and everything in it rather than worry about the internals of the language and what it loads (in that it can't load/touch anything outside the sandbox boundary anyway). It should be noted some of those weaknesses still apply to W11 and macOS even now. Seth Arnold wrote about this about ten years ago, touching on the problems back in 2.4.3 that prevented this from gaining traction. I'm surprised this hasn't been attempted already as it would be protective of those organisations massive cloud investments, too. Side note: A central signing authority would be really helpful in the Linux world, maybe run/funded by a consortium of Linux-using orgs (Microsoft/Amazon/Google/Red Hat). ![]() Proton is great, and Linux has only gotten more user-friendly over time, but there's still some touch points that are either stubbornly still not addressed or just won't be addressed because they're antithetical to FOSS (again, TPM and central signing authorities). On W11 you have TPM/ROT, centralised app signing (that you can enable/disable as you prefer), DirectX 12 (I realise this wouldn't matter if everything was on Vulkan, but it's not). ![]() I get where you're coming from, and if it's primarily a gaming machine it might not be something you care about, but there's a bunch of reasons why someone might prefer Windows 11 to a Linux system (I say this adoring Linux - so none of this is intended as criticism).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |