Node -webkit (nw.js) Ubuntu 12.04 LTS SUID sandbox error

I am creating nodewebkit and webrtc desktop applications for video streaming. During creation, I try to use the getusermedia API, but I get the following error in my Linux box.

[15464: 0224/125017: ERROR: browser_main_loop.cc (162)] Runs without an isolated SUID sandbox! See https://code.google.com/p/chro ... for more information on sandboxed development. ATTENTION: the default value of the force_s3tc_enable parameter is overridden by the environment.

With some help from google, I found out below the details of suid.

SUID (Set Owner User ID at Run) is a special type of file permissions granted to a file. Usually on Linux / Unix, when a program starts, it inherits access rights from a registered user. SUID is defined as granting temporary permissions to the user to run the program / file with the permissions of the owner of the file, and not to the user who runs it. In simple words, users will receive the permissions of the file owners, as well as the owner UID and GID when executing the file / program / command

In my opinion, node -webkit (nw.js) does not need a sandbox to run. Please correct me if I am wrong. I am running the same nw application on my Mac OS X Mavericks and it works flawlessly. I am really confused here because of the questions below.

  • Should I install a chrome sandbox before running nw on Linux (although I did not find such directives on the nw.js github page)?

  • If not, what changes do I need to make to Ubuntu 12.04 LTS so that my application does not request a sandbox?

+6
source share
2 answers

Try adding this to your package.json package:

"chromium-args": "--disable-setuid-sandbox" 

It will disable the sandbox on the chrome instance that uses nw.js.

+2
source

The message can be ignored, since the sandbox is not used / needed in node -webkit.

There is an error message in the error message .

+1
source

Source: https://habr.com/ru/post/982937/


All Articles