添加链接
link之家
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more

When I run chromium on --mo-sandbox, that mean have a way to access local system? I guess not?

Actually, I wonder why have not some fork for this project (Chromium), that give ability access local system/ For these situation that app run locally. In such way, we can run full application on browser without extra level as node (Electron or ECF. etc..).

Rather than, I not understand why not have JS lib to connect to database directly from the browser. Or at least from Webassembly?

Sandbox makes exploiting security holes very difficult. By default all the render processes including extensions will have sandbox enabled. Here's more on sandbox: chromium.googlesource.com/chromium/src/+/lkgr/docs/design/… Asesh Feb 15 '19 at 3:38 As time pass many developer realize that HTML render is the better way to build their UI for desktop app. So why we need build it with Electron on other complicated way. way not have ability to enter all functionality into chromium. We just need keep not browsing internet with this app, and we not need any Sandbox as every desktop application. Why we need build it upon Node or Embedded Chromium to achieve bypass to access local system? Matanya Cohen Feb 15 '19 at 8:08 I try be more concrete. For my desktop app, I need ability to send data directly to the Clipboard, Or I need write directly to File system. If I use with --no-sandbox tag I can achieve it? (Please don't tell me about the work around to do so. I just want the HTML ui, but I bot need any Sandbox). Matanya Cohen Feb 20 '19 at 6:47 Building desktop apps with Electron much more easier than dealing with Chromium's source code. You can use Node.js in Electron through which you will be able to access file system and even access clipboard too. I wouldn't use Chrome/Chromium for hosting desktop apps. Better use Electron Asesh Feb 20 '19 at 7:49

Thanks for contributing an answer to Stack Overflow!

  • Please be sure to answer the question . Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .