Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Is Confident In Security of Edge Browser

Posted by timothy on from the way-out-there-man dept.

jones_supa writes: It's no secret that Internet Explorer has always been criticized for its poor security, so with the Edge web browser (previously known as Spartan), Microsoft is trying to tackle this problem more effectively and make sure that users consider it at least as good as Chrome and Firefox. In a blog post, Microsoft details the security enhancements available in Edge, pointing out that most of the changes it made to the new browser make it much more secure than Internet Explorer. There is more protection against trickery, app containers are used as the sandbox mechanism, and protection against memory corruption is better. Old, insecure plugin interfaces are not supported at all: VML, VBScript, Toolbars, BHOs, and ActiveX are all nuked from the orbit.

4 of 133 comments (clear)

  1. How hard will this break Corp Intranet apps? by disposable60 · · Score: 5, Insightful

    So all those corporate intranet apps that stupidly require IE - how hard will Edge break those?

    --
    You're looking for quotes? See my journal.
    1. Re:How hard will this break Corp Intranet apps? by Shados · · Score: 5, Insightful

      hard enough that IE11 will still be supported for a while in parallel.

      Thats the whole point of Edge. So that Microsoft can have a real browser without leaving the big corps legacy shit behind.

    2. Re:How hard will this break Corp Intranet apps? by peragrin · · Score: 4, Insightful

      Why were you stupid enough to write apps that only ever worked in IE to begin with?

      Don't blame microsoft for your stupidity. We have enough to blame Microsoft for that is legitimately their fault.

      --
      i thought once I was found, but it was only a dream.
  2. Re:Talk the talk, but doesn't walk the walk... by gstoddart · · Score: 4, Insightful

    The problem is that new code is just that ... new and untested.

    So you build something new from scratch and say "wow, we did awesome at teh security". Well, OK, now you release it into the wild and wait for people to abuse it -- that's when you find out how well you've done.

    Any new code is going to have the problem, because it hasn't been field tested or through several iterations.

    It's all well and good for Microsoft to say "nailed it". That doesn't make it true. So I think it's probably safe to assume that unless Microsoft has done something remarkable, there's probably a bunch of places where they haven't fully locked it down.

    --
    Lost at C:>. Found at C.