Re: RFC: seccomp-bpf support
От | David Fetter |
---|---|
Тема | Re: RFC: seccomp-bpf support |
Дата | |
Msg-id | 20190828164750.GA21153@fetter.org обсуждение исходный текст |
Ответ на | RFC: seccomp-bpf support (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: RFC: seccomp-bpf support
|
Список | pgsql-hackers |
On Wed, Aug 28, 2019 at 11:13:27AM -0400, Joe Conway wrote: > SECCOMP ("SECure COMPuting with filters") is a Linux kernel syscall > filtering mechanism which allows reduction of the kernel attack surface > by preventing (or at least audit logging) normally unused syscalls. > > Quoting from this link: > https://www.kernel.org/doc/Documentation/prctl/seccomp_filter.txt > > "A large number of system calls are exposed to every userland process > with many of them going unused for the entire lifetime of the > process. As system calls change and mature, bugs are found and > eradicated. A certain subset of userland applications benefit by > having a reduced set of available system calls. The resulting set > reduces the total kernel surface exposed to the application. System > call filtering is meant for use with those applications." > > Recent security best-practices recommend, and certain highly > security-conscious organizations are beginning to require, that SECCOMP > be used to the extent possible. The major web browsers, container > runtime engines, and systemd are all examples of software that already > support seccomp. Neat! Are the seccomp interfaces for other kernels arranged in a manner similar enough to have a unified interface in PostgreSQL, or is this more of a Linux-only feature? Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-hackers по дате отправления: