Does Ozone require running Chromium with no sandbox?

32 views

Skip to first unread message

Olli Etuaho

unread,

Dec 9, 2015, 8:40:37 AM12/9/15

to ozon...@chromium.org

Hi, I'm looking at

https://www.chromium.org/developers/design-documents/ozone

and it suggests running Ozone builds with the setuid sandbox disabled. Is this some kind of a fundamental limitation of Ozone or some of the Ozone ports, or just documented there to save developers the hassle of setting up the sandbox?

This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Robert Kroeger

unread,

Dec 9, 2015, 3:00:12 PM12/9/15

to Olli Etuaho, ozon...@chromium.org

On Wednesday, December 9, 2015, Olli Etuaho <oet...@nvidia.com> wrote:

Hi, I'm looking at

https://www.chromium.org/developers/design-documents/ozone

and it suggests running Ozone builds with the setuid sandbox disabled. Is this some kind of a fundamental limitation of Ozone or some of the Ozone ports, or just documented there to save developers the hassle of setting up the sandbox?

Ozone runs just fine with the sandbox enabled -- production CrOS devices use ozone and have the sandbox on. During development, you may find it convenient to disable the sandbox because sometimes it makes debugging tricky.