-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SUID error #2699
Comments
This can be ignored, since we don't use renderer sandbox in node-webkit. I'll remove this message. |
That would really be great… because 6 months later, it’s still annoying the hell out of users! ;) |
Please up! |
Please fix it. It is annoying. |
What about enabling sandboxing instead of hiding a security warning? |
That would really be great if you fix it.It still annoying. |
I don't like the tone of @jvoisin's comment, but it would be nice to get some insight on why the sandbox is not enabled. Does the sandbox prevent some features of nw.js from working? Do you get better performance by keeping it off? What are the security implications of having the sandbox disabled? Would it be better to enable the sandbox? |
I think you can't have the sandbox if you expect node to be able to change things on your system, like using |
This is really annoying, please fix it. |
Please fix it |
It's fixed in 0.13.0 beta version. |
Hello, This error is shown when I start my simple "Hello World" app on Linux x64, Ubuntu 14.04.
[24035:1126/185148:ERROR:browser_main_loop.cc(162)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
I don't know what might be the cause of this error.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: