seccomp

From Wikipedia, the free encyclopedia

Template:Short description

Page Module:Message box/ambox.css has no content.

Page Module:Infobox/styles.css has no content.

seccomp
[[Programmer|Original authorTemplate:Pluralize from text]]Andrea Arcangeli
Initial releaseMarch 8, 2005; 21 years ago (2005-03-08)
Template:Infobox software/simple
Written inC
Operating systemLinux
TypeSandboxing
LicenseGNU General Public License
Websitecode.google.com/archive/p/seccompsandbox/wikis/overview.wiki

Script error: No such module "Check for conflicting parameters".

seccomp (short for secure computing[1]) is a computer security facility in the Linux kernel. 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 either just log the event or terminate the process with SIGKILL or SIGSYS.[2][3] In this sense, it does not virtualize the system's resources but isolates the process from them entirely.

seccomp mode is enabled via the Template:Man system call using the PR_SET_SECCOMP argument, or (since Linux kernel 3.17[4]) via the Template:Man system call.[5] seccomp mode used to be enabled by writing to a file, /proc/self/seccomp, but this method was removed in favor of prctl().[6] In some kernel versions, seccomp disables the RDTSC x86 instruction, which returns the number of elapsed processor cycles since power-on, used for high-precision timing.[7]

seccomp-bpf is an extension to seccomp[8] that allows filtering of system calls using a configurable policy implemented using Berkeley Packet Filter rules. It is used by OpenSSH[9] and vsftpd as well as the Google Chrome/Chromium web browsers on ChromeOS and Linux.[10] (In this regard seccomp-bpf achieves similar functionality, but with more flexibility and higher performance, to the older systrace—which seems to be no longer supported for Linux.)

Some consider seccomp comparable to OpenBSD pledge(2) and FreeBSD capsicum(4)[citation needed].

History

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. It was merged into the Linux kernel mainline in kernel version 2.6.12, which was released on March 8, 2005.[11]

Software using seccomp or seccomp-bpf

  • Android uses a seccomp-bpf filter in the zygote since Android 8.0 Oreo.[12]
  • systemd's sandboxing options are based on seccomp.[13]
  • QEMU, the Quick Emulator, the core component to the modern virtualization together with KVM uses seccomp on the parameter --sandbox[14]
  • Docker – software that allows applications to run inside of isolated containers. Docker can associate a seccomp profile with the container using the --security-opt parameter.
  • Arcangeli's CPUShare was the only known user of seccomp for a while.[15] Writing in February 2009, Linus Torvalds expresses doubt whether seccomp is actually used by anyone.[16] However, a Google engineer replied that Google is exploring using seccomp for sandboxing its Chrome web browser.[17][18]
  • Firejail is an open source Linux sandbox program that utilizes Linux namespaces, Seccomp, and other kernel-level security features to sandbox Linux and Wine applications.[19]
  • As of Chrome version 20, seccomp-bpf is used to sandbox Adobe Flash Player.[20]
  • As of Chrome version 23, seccomp-bpf is used to sandbox the renderers.[21]
  • Snap specify the shape of their application sandbox using "interfaces" which snapd translates to seccomp, AppArmor and other security constructs[22]
  • vsftpd uses seccomp-bpf sandboxing as of version 3.0.0.[23]
  • OpenSSH has supported seccomp-bpf since version 6.0.[9]
  • Mbox uses ptrace along with seccomp-bpf to create a secure sandbox with less overhead than ptrace alone.[24]
  • LXD, a Ubuntu "hypervisor" for containers[25][26]
  • Firefox and Firefox OS, which use seccomp-bpf[27][28]
  • Tor supports seccomp since 0.2.5.1-alpha[29]
  • Lepton, a JPEG compression tool developed by Dropbox uses seccomp[30]
  • Kafel is a configuration language, which converts readable policies into seccompb-bpf bytecode[31]
  • Subgraph OS uses seccomp-bpf[32][33]
  • Flatpak uses seccomp for process isolation[34]
  • Bubblewrap is a lightweight sandbox application developed from Flatpak[35]
  • minijail[36] uses seccomp for process isolation[37]
  • SydBox uses seccomp-bpf[38] to improve the runtime and security of the ptrace sandboxing used to sandbox package builds on Exherbo Linux distribution.
  • File, a Unix program to determine filetypes, uses seccomp to restrict its runtime environment[39]
  • Zathura, a minimalistic document viewer, uses seccomp filter to implement different sandbox modes[40]
  • Tracker, a indexing and preview application for the GNOME desktop environment, uses seccomp to prevent automatic exploitation of parsing vulnerabilities in media files[41]

See also

References

Page Template:Reflist/styles.css has no content.

  1. ^ Template:Man
  2. ^ Page Module:Citation/CS1/styles.css has no content.Corbet, Jonathan (2015-09-02). "A seccomp overview". lwn. Retrieved 2017-10-05.
  3. ^ Page Module:Citation/CS1/styles.css has no content."Documentation/prctl/seccomp_filter.txt". Retrieved 2017-10-05.
  4. ^ Page Module:Citation/CS1/styles.css has no content."Linux kernel 3.17, Section 11. Security". kernelnewbies.org. 2013-10-05. Retrieved 2015-03-31.
  5. ^ Page Module:Citation/CS1/styles.css has no content."seccomp: add "seccomp" syscall". kernel/git/torvalds/linux.git - Linux kernel source tree. kernel.org. 2014-06-25. Retrieved 2014-08-22.
  6. ^ Page Module:Citation/CS1/styles.css has no content.Arcangeli, Andrea (2007-06-14). "[PATCH 1 of 2] move seccomp from /proc to a prctl". Retrieved 2013-08-02.
  7. ^ Page Module:Citation/CS1/styles.css has no content.Tinnes, Julien (2009-05-28). "Time-stamp counter disabling oddities in the Linux kernel". cr0 blog. Retrieved 2013-08-02.
  8. ^ Page Module:Citation/CS1/styles.css has no content.Corbet, Jonathan (2012-01-11). "Yet another new approach to seccomp". lwn. Retrieved 2013-08-02.
  9. ^ a b Page Module:Citation/CS1/styles.css has no content."Openssh 6.0 release notes". Retrieved 2013-10-14.
  10. ^ Page Module:Citation/CS1/styles.css has no content.Tinnes, Julien (2012-11-19). "A safer playground for your Linux and Chrome OS renderers". The Chromium Blog. Retrieved 2013-08-02.
  11. ^ Page Module:Citation/CS1/styles.css has no content."[PATCH] seccomp: secure computing support". Linux kernel history. Kernel.org git repositories. 2005-03-08. Retrieved 2013-08-02.{{cite web}}: CS1 maint: deprecated archival service (link)
  12. ^ Page Module:Citation/CS1/styles.css has no content."Seccomp filter in Android O". Android Developers Blog.
  13. ^ Page Module:Citation/CS1/styles.css has no content."systemd.exec — Execution environment configuration". freedesktop.org. Retrieved 2017-10-14.
  14. ^ Page Module:Citation/CS1/styles.css has no content.Otubo, Eduardo (2017-09-15). "QEMU Sandboxing new model pull request". qemu-devel mailing list archive.
  15. ^ Page Module:Citation/CS1/styles.css has no content.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.
  16. ^ Page Module:Citation/CS1/styles.css has no content.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.
  17. ^ Page Module:Citation/CS1/styles.css has no content.Gutschke, Markus (2009-05-06). "Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole". Retrieved 2013-08-02.
  18. ^ Page Module:Citation/CS1/styles.css has no content.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.
  19. ^ Page Module:Citation/CS1/styles.css has no content."Firejail". Firejail. Retrieved 2016-11-26.
  20. ^ Page Module:Citation/CS1/styles.css has no content.Evans, Chris (2012-07-04). "Chrome 20 on Linux and Flash sandboxing". Retrieved 2013-08-02.
  21. ^ Page Module:Citation/CS1/styles.css has no content.Tinnes, Julien (2012-09-06). "Introducing Chrome's next-generation Linux sandbox". cr0 blog. Retrieved 2013-08-02.
  22. ^ Page Module:Citation/CS1/styles.css has no content."Snap security policy". Archived from the original on 2017-02-04. Retrieved 2017-02-03.
  23. ^ Page Module:Citation/CS1/styles.css has no content.Evans, Chris (2012-04-09). "vsftpd-3.0.0 and seccomp filter sandboxing is here!". Retrieved 2013-08-02.
  24. ^ Page Module:Citation/CS1/styles.css has no content."MBOX". Retrieved 2014-05-20.
  25. ^ Page Module:Citation/CS1/styles.css has no content."LXD an "hypervisor" for containers (based on liblxc)". 4 November 2014. Retrieved 2014-11-08.
  26. ^ Page Module:Citation/CS1/styles.css has no content."Where We're Going With LXD". Retrieved 2014-11-08.
  27. ^ Page Module:Citation/CS1/styles.css has no content.Destuynder, Guillaume (2012-09-13). "Firefox Seccomp sandbox". Mozilla Bugzilla. Retrieved 2015-01-13.
  28. ^ Page Module:Citation/CS1/styles.css has no content.Destuynder, Guillaume (2012-09-13). "Firefox Seccomp sandbox". Mozilla Wiki. Retrieved 2015-01-13.
  29. ^ Page Module:Citation/CS1/styles.css has no content."Tor ChangeLog".
  30. ^ Page Module:Citation/CS1/styles.css has no content."Lepton image compression: saving 22% losslessly from images at 15MB/s". Dropbox Tech Blog. Retrieved 2016-07-15.
  31. ^ Page Module:Citation/CS1/styles.css has no content."Kafel: A language and library for specifying syscall filtering policies".
  32. ^ Page Module:Citation/CS1/styles.css has no content."Subgraph OS". Subgraph. Retrieved 2016-12-18.
  33. ^ Page Module:Citation/CS1/styles.css has no content."LoganCIJ16: Future of OS". YouTube. Archived from the original on 2021-12-21. Retrieved 2016-12-18.
  34. ^ Page Module:Citation/CS1/styles.css has no content."The flatpak security model – part 1: The basics". Retrieved 2017-01-21.
  35. ^ Page Module:Citation/CS1/styles.css has no content."bubblewrap". Retrieved 2018-04-14.
  36. ^ Page Module:Citation/CS1/styles.css has no content."Chromium OS Sandboxing - the Chromium Projects".
  37. ^ Page Module:Citation/CS1/styles.css has no content."Minijail [LWN.net]". lwn.net. Retrieved 2017-04-11.
  38. ^ Page Module:Citation/CS1/styles.css has no content."core/trace/use_seccomp". dev.exherbo.org. Retrieved 2021-05-31.
  39. ^ Page Module:Citation/CS1/styles.css has no content."File application Sandboxing". GitHub.
  40. ^ Page Module:Citation/CS1/styles.css has no content."Zathura seccomp implementation".
  41. ^ Page Module:Citation/CS1/styles.css has no content."Gnome tracker seccomp implementation".

Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found. Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.

Retrieved from "https://cosmopedia.co/index.php?title=Seccomp&oldid=1286156"