Why is there "seccomp" events related to Google Chrome in syslog?
It's just the kernel logging audit events of seccomp from Chrome's sandbox.
From Wikipedia:
seccomp (short for secure computing mode) is a simple sandboxing mechanism for the Linux kernel. It was added in Linux kernel 2.6.12 in March 8, 2005.
It 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.
Google is exploring using seccomp for sandboxing its Chrome web browser.
As of Chrome version 20, seccomp is used to sandbox Adobe Flash Player. As of Chrome version 23, seccomp is used to sandbox the renderers.
See also:
- Chrome 20 on Linux and Flash sandboxing
- Introducing Chrome's next-generation Linux sandbox
- A safer playground for your Linux and Chrome OS renderers