Live data from Hacker News

Strengthening the Microsoft Edge Sandbox

blogs.windows.com

1–10 of 58 posts

Re: Strengthening the Microsoft Edge Sandbox

#2
From the comments section:

"I want to support MS, I’m a development partner. But I feel like you guys spend way too much time thinking about how to push intrusive ad’s into the OS and trying to get easy ad-based revenue from your browser: Talking very good security talk but not walking a very good security walk."

The commenter also makes a comment about how Chrome the older browser was found to be much more secure than Edge the newer one. And then a bunch of technical stuff from someone responding to it (the respondent is not the person writing the article).

Am I the only one who feels MSFT would simply be better off not writing these articles at all if they don't particularly care for engaging with their audience?

Oh, and you can't leave a comment without signing in with a Microsoft account. :-)

Re: Strengthening the Microsoft Edge Sandbox

#3

From the comments section: "I want to support MS, I’m a development partner. But I feel like you guys spend way too much time thinking about how to push intrusive ad’s into the OS and trying to get easy ad-based revenue from your browser: Talking very good security talk but not walking a very good security walk." The commenter also makes a comment about how Chrome the older browser was found to be much more secure th…

[deleted]

Re: Strengthening the Microsoft Edge Sandbox

#5
Is the AC Access Scope whitelisting described in the article available to all UWP apps in the Creators Update?

I understand it was added specifically for Edge sandboxing, but it sounds like useful functionality (albeit niche) for other apps that deal with untrusted data routinely.

PS - In terms of technology and standards Edge is a pretty solid browser. I love the Dark theme.

Re: Strengthening the Microsoft Edge Sandbox

#7

Is the AC Access Scope whitelisting described in the article available to all UWP apps in the Creators Update? I understand it was added specifically for Edge sandboxing, but it sounds like useful functionality (albeit niche) for other apps that deal with untrusted data routinely. PS - In terms of technology and standards Edge is a pretty solid browser. I love the Dark theme.

Yeah, actually app container tech is available to any native developer. (Maybe there's a .Net API for dealing with them. Don't know.)

Re: Strengthening the Microsoft Edge Sandbox

#8
post #4

just checked my website visitor log. Only 1% people use Edge. It is not a surprise at all. The best way to secure a browser is just like what chrome and firefox do: open source it.

Chrome isn't Open Source. Chromium is Open Source.

Chrome adds a lot of proprietary bits including (but not limited to): Audio & Video Codecs, Flash Plugin, Crash Reporting, Metrics, et al.

Re: Strengthening the Microsoft Edge Sandbox

#9

Is the AC Access Scope whitelisting described in the article available to all UWP apps in the Creators Update? I understand it was added specifically for Edge sandboxing, but it sounds like useful functionality (albeit niche) for other apps that deal with untrusted data routinely. PS - In terms of technology and standards Edge is a pretty solid browser. I love the Dark theme.

Yeah, actually app container tech is available to any native developer. (Maybe there's a .Net API for dealing with them. Don't know.)

I wasn't asking about app containers in general. I was asking specifically about the AC Access Scope whitelisting discussed in the article.

Essentially the thing they added in the Creators Update and are discussing here.

Re: Strengthening the Microsoft Edge Sandbox

#10
post #4

just checked my website visitor log. Only 1% people use Edge. It is not a surprise at all. The best way to secure a browser is just like what chrome and firefox do: open source it.

Chrome isn't Open Source. Chromium is Open Source. Chrome adds a lot of proprietary bits including (but not limited to): Audio & Video Codecs, Flash Plugin, Crash Reporting, Metrics, et al.

And not to mention: DRM.

No thanks.

Post reply on HN