3 ms·

You'd be correct! https://docs.microsoft.com/en-us/windows/win32/winstation/window-station-security-and-access-rights https://docs.microsoft.com/en-us/windows/

You'd be correct! https://docs.microsoft.com/en-us/windows/win32/winstation/window-station-security-and-access-rights https://docs.microsoft.com/en-us/windows/win32/winstation/wi... https://docs.microsoft.com/en-us/windows/win32/winstation/desktop-security-and-access-rights https://docs.microsoft.com/en-us/windows/win32/winstation/de... https://docs.microsoft.com/en-us/windows/win32/procthread/process-security-and-access-rights https://docs.microsoft.com/en-us/windows/win32/procthread/pr... https://docs.microsoft.com/en-us/windows/win32/procthread/thread-security-and-access-rights https://docs.microsoft.com/en-us/windows/win32/procthread/th... https://docs.microsoft.com/en-us/windows/win32/fileio/file-security-and-access-rights https://docs.microsoft.com/en-us/windows/win32/fileio/file-s... Here https://news.ycombinator.com/item?id=31092978 https://news.ycombinator.com/item?id=31092978 suggests its not possible to prevent code injection aka system or app hooks. Preventing system and app hooks is very possible and the MS api's gve you all you need to block them, people just need to come up with innovative ways to deploy them!

qzw 4y ago
I don't think the comment by wfh is saying that it's not possible to prevent these hooks. In fact, wfh is saying the opposite, i.e. that they already have the mitigation in place, but cannot enable it because there are legitimate use cases for hooking/injection, and users who use programs that depend on these techniques would be (rightly) upset if Chrome unilaterally decided to block all such use cases. The comment is lamenting the fact that the author of the blog post is creating yet more such use cases and will make it even harder for Chrome to ever enable the feature to prevent code injection.