3 ms·
Then watch all that hard work get undone the next time Microsoft forces an update and bundles a "fixed" dnsapi.dll with some other important security fix. Are
by pdkl95 11y ago
Then watch all that hard work get undone the next time Microsoft forces an update and bundles a "fixed" dnsapi.dll with some other important security fix.
Are you going to verify that there isn't a new backdoor in every single update that works around your changes? Or are you going to bypass that impossible task by not installing any future security updates?
Workarounds that try to make a hostile OS "safe" is doomed always having to play catch-up, and Microsoft can probably add problems faster than you can find them.
- userbinator 11y agoThe real question is how often does dnsapi.dll change, and when it does, can you reapply your patches? The crackers were quite successful in bypassing the activation scheme for previous versions and made autopatchers that would find and patch the right places, in a generic way that worked across many versions, so I'm reasonably certain that this could be done to preserve privacy too. And with more people on their side now than just pirates, there's all the more reason to do it. It's essentially taking the files that would be changed in an update and passing them through a filter that automatically maintains the pieces you want.