<p><span class="h-card" translate="no"><a href="https://mastodon.online/@Eunakria" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Eunakria</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@thelinuxEXP" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>thelinuxEXP</span></a></span> <span class="h-card" translate="no"><a href="https://twit.social/@bouncing" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bouncing</span></a></span> <span class="h-card" translate="no"><a href="https://hachyderm.io/@breiter" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>breiter</span></a></span> One could argue that Microsoft should do their utmost to reduce the risk of this happening, which includes providing API's that makes it harder for a third-party to do the wrong thing.</p><p>They'll never be able to <em>eliminate</em> it though. To do that, they need a Iphone-level lockdown of the operating system, which no same person should ever consider a good thing.</p><p>eBPF is one of those things, I think. A lot of things that would otherwise require a dangerous kernel module can be achieved using eBPF.</p><p>Windows probably needs more of that?</p>