From Wikipedia, the free encyclopedia
Jump to: navigation, search
Original author(s) Andrea Arcangeli
Initial release March 8, 2005; 10 years ago (2005-03-08)
Development status mainlined
Written in C
Operating system Linux
Type Sandboxing
License GNU General Public License

seccomp (short for secure computing mode) is a computer security facility that provides an application sandboxing mechanism in the Linux kernel; it was merged into the Linux kernel mainline in kernel version 2.6.12, which was released on March 8, 2005.[1] seccomp allows a process to make a one-way transition into a "secure" state where it cannot make any system calls except exit(), sigreturn(), read() and write() to already-open file descriptors. Should it attempt any other system calls, the kernel will terminate the process with SIGKILL. In this sense, it does not virtualize the system's resources but isolates the process from them entirely.

seccomp mode is enabled via the prctl(2) system call using the PR_SET_SECCOMP argument, or (since Linux kernel 3.17[2]) via the seccomp(2) system call.[3] seccomp mode used to be enabled by writing to a file, /proc/self/seccomp, but this method was removed in favor of prctl().[4] In some kernel versions, seccomp disables the RDTSC x86 instruction.[clarification needed][5]

seccomp-bpf is an extension to seccomp[6] that allows filtering of system calls using a configurable policy implemented using Berkeley Packet Filter rules. It is used by OpenSSH and vsftpd as well as the Google Chrome/Chromium web browsers on Chrome OS and Linux.[7]

Software products that use seccomp include the following:

  • seccomp was first devised by Andrea Arcangeli in January 2005 for use in public grid computing and was originally intended as a means of safely running untrusted compute-bound programs.
  • Arcangeli's CPUShare was the only known user of this feature.[8] Writing in February 2009, Linus Torvalds expresses doubt whether seccomp is actually used by anyone.[9] However, a Google engineer replied that Google is exploring using seccomp for sandboxing its Chrome web browser.[10][11]
  • As of Chrome version 20, seccomp-bpf is used to sandbox Adobe Flash Player.[12]
  • As of Chrome version 23, seccomp-bpf is used to sandbox the renderers.[13]
  • Vsftpd uses seccomp-bpf sandboxing as of version 3.0.0.[14]
  • OpenSSH has supported seccomp-bpf since version 6.0.[15]
  • Mbox uses ptrace along with seccomp-bpf to create a secure sandbox with less overhead than ptrace alone.[16]
  • LXD, which is a "hypervisor" for containers[17][18]
  • Firefox and FirefoxOS use seccomp-bpf to sandbox the child processes and certain plugins.[19][20]
  • Cjdns uses seccomp-bpf as one of its sandbox mechanisms, filtering the system calls it performs on a Linux system, and strictly limiting its access to the outside world.[21]
  • Tor supports seccomp since[22]


  1. ^ "[PATCH] seccomp: secure computing support". Linux kernel history. git repositories. 2005-03-08. Retrieved 2013-08-02. 
  2. ^ "Linux kernel 3.17, Section 11. Security". 2013-10-05. Retrieved 2015-03-31. 
  3. ^ "seccomp: add "seccomp" syscall". kernel/git/torvalds/linux.git - Linux kernel source tree. 2014-06-25. Retrieved 2014-08-22. 
  4. ^ Arcangeli, Andrea (2007-06-14). "[PATCH 1 of 2] move seccomp from /proc to a prctl". Retrieved 2013-08-02. 
  5. ^ Tinnes, Julien (2009-05-28). "Time-stamp counter disabling oddities in the Linux kernel". cr0 blog. Retrieved 2013-08-02. 
  6. ^ Corbet, Jonathan (2012-01-11). "Yet another new approach to seccomp". lwn. Retrieved 2013-08-02. 
  7. ^ Tinnes, Julien (2012-11-19). "A safer playground for your Linux and Chrome OS renderers". The Chromium Blog. Retrieved 2013-08-02. 
  8. ^ van de Ven, Arjan (2009-02-28). "Re: [stable] [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole". Linux Kernel Mailing List. Retrieved 2013-08-02. 
  9. ^ Torvalds, Linus (2009-02-28). "Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole". Linux Kernel Mailing List. Retrieved 2013-08-02. 
  10. ^ Gutschke, Markus (2009-05-06). "Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole". Retrieved 2013-08-02. 
  11. ^ Gutschke, Markus (2009-05-06). "Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole". Linux Kernel Mailing List. Retrieved 2013-08-02. 
  12. ^ Evans, Chris (2012-07-04). "Chrome 20 on Linux and Flash sandboxing". Retrieved 2013-08-02. 
  13. ^ Tinnes, Julien (2012-09-06). "Introducing Chrome's next-generation Linux sandbox". cr0 blog. Retrieved 2013-08-02. 
  14. ^ Evans, Chris (2012-04-09). "vsftpd-3.0.0 and seccomp filter sandboxing is here!". Retrieved 2013-08-02. 
  15. ^ "Openssh 6.0 release notes". Retrieved 2013-10-14. 
  16. ^ "MBOX". Retrieved 2014-05-20. 
  17. ^ "LXD an "hypervisor" for containers (based on liblxc)". Retrieved 2014-11-08. 
  18. ^ "Where We're Going With LXD". Retrieved 2014-11-08. 
  19. ^ Destuynder, Guillaume (2012-09-13). "Firefox Seccomp sandbox". Mozilla Bugzilla. Retrieved 2015-01-13. 
  20. ^ Destuynder, Guillaume (2012-09-13). "Firefox Seccomp sandbox". Mozilla Wiki. Retrieved 2015-01-13. 
  21. ^ DeLisle, Caleb James (2014-09-24). "Added SECCOMP sandboxing and new admin API call to check if permissions are properly dropped". Github. Retrieved 2015-09-24. 
  22. ^ "Tor ChangeLog". 

External links[edit]