Security implications of Chrome/Chromium running suid root (Linux, possibly BSD), which is required for raw sockets.

[nl255]

In order to be able to use raw sockets on Linux (and presumably BSD) a program must be run with root privileges which means making Chrome/Chromium suid root. Even if said privileges are dropped immediately after setting CAP_NET_RAW (and presumably CAP_NET_ADMIN for setting promiscuous mode and/or mac spoofing) the security risks are still significantly higher than not having it run as root at all.

[osmarks]

The proposal appears to mean "TCP/UDP sockets", which are "raw" compared to websockets and HTTP I guess, and not actual raw system sockets. Perhaps it could be renamed to clarify this Apparently someone thought of that, see #10.

[ewilligers]

The confusion will be avoided when #10 is resolved.