On Wed, Nov 23, 2011 at 7:12 PM, wrote:
>>>>>> "YP" == Yves-Alexis Perez writes:
> YP> I'm not sure telling people to use --no-sandbox without telling them
> YP> what they lose is a good idea. Sandboxing is here for a reason.
I find the "no-sandbox" label sufficiently descriptive, but for
completeness sake, this option will (as it sounds) disable chromium's
process isolating "sandbox" feature. This means that the security
hardening feature, which normally makes it very hard for data to leak
between chromium processes (i.e. tabs), will be off.
It is of course not a permanent solution.
> Wish it was documented. Say on the man page.
You're certainly free to create a patch with that documented
problem is that chromium commands change rapidly. It may be better
just to link to this page, which gets updated fairly regularly:
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Archive: CANTw=MP53P7uuVFYiMGZcjyWuYCoM=3gncb3VLLiBhF5KtrxQ Q@mail.gmail.com">http://lists.debian.org/CANTw=MP53P7uuVFYiMGZcjyWuYCoM=3gncb3VLLiBhF5KtrxQ Q@mail.gmail.com