• JoYo@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    13
    ·
    1 year ago

    Edge is using EMET for memory protections.

    Chrome has EMET disabled because it’s own memory protections conflict and it just won’t execute.

    When you’re make a web view for Windows you’re either bringing a long your own rendering or using Edge because it’s included.

    No one wants to secure their own rendering which is why they all use whatever is already there which is EMET which is a pita to test so they just go with Edge.

    native is just jargon for “what is already there.”

    • pivot_root@lemmy.world
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      EMET? The framework that was end-of-lifed in 2018? I’d bloody well hope Chrome doesn’t use something that isn’t supported anymore.

      Chrome’s sandboxing is weird and prone to breaking, but at least it isn’t stuck relying entirely on a kernel framework exclusive to an OS that people are extremely hesitant to keep up-to-date.