diff options
| author | obadz <obadz-git@obadz.com> | 2016-08-04 20:26:05 +0100 |
|---|---|---|
| committer | obadz <obadz-git@obadz.com> | 2016-08-04 20:37:35 +0100 |
| commit | 33557acb36ffb60317775ab7fdb3451a47b69d62 (patch) | |
| tree | 66fe8ae76c7b927d43946f719108b8bacbe64e4e /pkgs/development/python-modules/python-sql | |
| parent | 672447f1ada85a38f1b1f7d909d72977658abcb4 (diff) | |
chromium: add ability to control which sandbox is used
First step towards addressing #17460
In order to be able to run the SUID sandbox, which is good for security
and required to run Chromium with any kind of reasonable sandboxing when
using grsecurity kernels, we want to be able to control where the
sandbox comes from in the Chromium wrapper. This commit patches the
appropriate bit of source and adds the same old sandbox to the wrapper
(so it should be a no-op)
Diffstat (limited to 'pkgs/development/python-modules/python-sql')
0 files changed, 0 insertions, 0 deletions