-
Notifications
You must be signed in to change notification settings - Fork 546
Chrome Sandbox is disabled in electron. Is this secure? #19
Comments
Nice article! There has been a follow-up blogpost mentioning the now implemented fixes and also the official security guide. |
Thanks @wanderer for bringing this up, and thanks @pguth for the useful followups. To recap: the Chromium sandbox is an extra layer of protection around the Web platform sandboxing. It protects from exploits against the Web platform's implementation. Electron doesn't have it enabled. In my opinion, It is a security concern, but not a critical one. We should track its status, and possibly copy from Brave's solution when Beaker is more mature. |
I would rather rephrase to: It is a critical security concern but we can _carefully_ manage for the time of initial development because: a) it seems the development is going quickly. In the words of the electron security guide:
It closes with:
@pfraze: Sorry for the wrong impression my first post gave. |
@pguth Calling this critical obscures the nature of the issue. Calling it critical makes it sound like there's a known vector to escape the Web API sandbox. That's not the case. The issue is, if there is a vulnerability in the Web API or plugin system, there's no process-level sandbox to contain that failure. Otherwise, we're in agreement. Before Beaker can be considered a mature browser, it'll need to adopt a process-level sandbox. |
Ah, I see. |
Important progress made by electron recently: electron/electron#6919 There may still need to be more work before I can adopt that flag here. Tracking issue: electron/electron#6712 |
The process-level sandbox is now enabled |
The Chromium sandbox was basically ripped out of electron. Is this a security concern to beaker?
Ref: http://blog.scottlogic.com/2016/03/09/As-It-Stands-Electron-Security.html
The text was updated successfully, but these errors were encountered: