summaryrefslogtreecommitdiffstats
path: root/sandbox/linux/seccomp/sandbox.cc
Commit message (Expand)AuthorAgeFilesLines
* Pull seccomp-sandbox in via DEPS rather than using an in-tree copy mseaborn@chromium.org2010-09-011-838/+0
* Revert 57921 - Pull seccomp-sandbox in via DEPS rather than using an in-tree ...nsylvain@chromium.org2010-08-311-0/+838
* Pull seccomp-sandbox in via DEPS rather than using an in-tree copymseaborn@chromium.org2010-08-301-838/+0
* Add support for calling {rt_,}sigaction(), and for invoking signal handlersmarkus@chromium.org2010-05-181-29/+190
* Prevent FPU state corruption by directly creating the signal frame on themarkus@chromium.org2010-05-111-36/+5
* Added support for sigreturn() and rt_sigreturn(). On x86-32, this ismarkus@chromium.org2010-04-281-79/+140
* Make the use of signals inside of the sandbox safe.markus@chromium.org2010-04-201-18/+136
* - Add a custom allocator for STL objects. This fixes sandbox failures thatmarkus@chromium.org2010-03-081-12/+17
* Be more restrictive when finding file names for libraries that need patching.markus@chromium.org2010-02-241-2/+17
* Allow the seccomp sandbox to be enabled, even if the suid sandbox hasmarkus@chromium.org2009-11-071-9/+34
* Only enable the seccomp sandbox, if the machine actually has kernel support formarkus@chromium.org2009-11-041-1/+55
* GCC's optimizer is getting more aggressive. It is no longer goodmarkus@chromium.org2009-10-221-0/+7
* - found all symbols that we directly access from assembly and marked them as ...markus@chromium.org2009-10-211-5/+7
* Fix minor compilation issues that can trigger on some platforms (e.g. CentOS)markus@chromium.org2009-09-141-1/+1
* Fix seccomp sandbox for gcc44markus@chromium.org2009-08-121-1/+1
* Initial version of the Seccomp sandbox. Imported from http://code.google.com/...markus@chromium.org2009-08-111-0/+421