summaryrefslogtreecommitdiffstats
path: root/sandbox/linux/seccomp/sandbox_impl.h
Commit message (Expand)AuthorAgeFilesLines
* Pull seccomp-sandbox in via DEPS rather than using an in-tree copy mseaborn@chromium.org2010-09-011-715/+0
* Revert 57921 - Pull seccomp-sandbox in via DEPS rather than using an in-tree ...nsylvain@chromium.org2010-08-311-0/+715
* Pull seccomp-sandbox in via DEPS rather than using an in-tree copymseaborn@chromium.org2010-08-301-715/+0
* Seccomp sandbox: Add a policy flag to allow file namespace access to be disabledmseaborn@chromium.org2010-08-271-0/+11
* Remove <iostream> where possible.erg@google.com2010-07-201-1/+0
* Add support for calling {rt_,}sigaction(), and for invoking signal handlersmarkus@chromium.org2010-05-181-0/+26
* Added support for sigreturn() and rt_sigreturn(). On x86-32, this ismarkus@chromium.org2010-04-281-1/+1
* Merged Mark Seaborn's changes:markus@chromium.org2010-04-221-25/+25
* Make the use of signals inside of the sandbox safe.markus@chromium.org2010-04-201-61/+75
* linux: turn on -Wextraevan@chromium.org2010-03-261-1/+1
* Revert "linux: turn on -Wextra"evan@chromium.org2010-03-251-1/+1
* linux: turn on -Wextraevan@chromium.org2010-03-251-1/+1
* - Add a custom allocator for STL objects. This fixes sandbox failures thatmarkus@chromium.org2010-03-081-1/+4
* Treat calls to lstat() and lstat64() the same as calls to stat(). In practise,markus@chromium.org2010-02-241-0/+6
* Allow the seccomp sandbox to be enabled, even if the suid sandbox hasmarkus@chromium.org2009-11-071-6/+19
* Only enable the seccomp sandbox, if the machine actually has kernel support formarkus@chromium.org2009-11-041-0/+10
* - found all symbols that we directly access from assembly and marked them as ...markus@chromium.org2009-10-211-3/+16
* Despite the futex(2) manual page telling us to include <linux/futex.h>, thismarkus@chromium.org2009-09-141-1/+0
* Initial version of the Seccomp sandbox. Imported from http://code.google.com/...markus@chromium.org2009-08-111-0/+621