3 ms·
Would this prevent me from looking at or modifying the Javascript code that is running, since it's already compiled?
by alexb_ 4y ago
Would this prevent me from looking at or modifying the Javascript code that is running, since it's already compiled?
- fluidcruft 4y agoHmmm. Maybe I misunderstood the link or missed something. I thought all they did is disable JIT and leave the JS as interpreted.
- alexb_ 4y agoI'm not knowledgable with JS at all, so you're probably right. I do wonder what the "Code Integrity Guard" is going to mean - who has to sign the JS? Does this mean tampermonkey/adblock scripts would stop working? Genuinely asking as like I said I don't really know too much about javascript
- wzdd 4y agoThis seems to be referring to https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/exploit-protection-reference?view=o365-worldwide#code-integrity-guard https://docs.microsoft.com/en-us/microsoft-365/security/defe... which would mean that they require the browser itself to be digitally signed, not the JS.
- genezeta 4y agoThis is a completely different thing. The "super duper secure mode" is not at all about you accessing or modifying the JS code from a website you are visiting. What it is about is trying to protect against some piece of JS code bypassing the security of the browser sandbox and accessing stuff it shouldn't ever have access to. :) Edit: Also, in general, no, disabling JIT would not prevent any particular JS code or extension from running. At most, it might mean some code would run slower. But that's what they claim, that it isn't noticeable.
- alexb_ 4y agoThanks for the clarification.