CONFIG_SECCOMP:

General informations

The Linux kernel configuration item CONFIG_SECCOMP has multiple definitions:

found in arch/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt:
• type: bool
• depends on: CONFIG_HAVE_ARCH_SECCOMP
• defined in arch/Kconfig
• found in Linux kernels: 5.10–5.19, 6.0–6.17, 6.18-rc+HEAD

Help text

This kernel feature is useful for number crunching applications that may need to handle untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP) or the seccomp() syscall, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y.

Enable seccomp to safely compute untrusted bytecode found in arch/loongarch/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/loongarch/Kconfig
• found in Linux kernels: 5.19, 6.0–6.7, 6.8-rc+HEAD

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/xtensa/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/xtensa/Kconfig
• found in Linux kernels: 5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

Enable seccomp to safely compute untrusted bytecode found in arch/x86/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/x86/Kconfig
• found in Linux kernels: 2.6.24–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/um/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/um/Kconfig
• found in Linux kernels: 4.19–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y.

Enable seccomp to safely compute untrusted bytecode found in arch/sparc/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_SPARC64 && CONFIG_PROC_FS
• defined in arch/sparc/Kconfig
• found in Linux kernels: 2.6.29–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/sh/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/sh/Kconfig
• found in Linux kernels: 2.6.27–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say N.

Enable seccomp to safely compute untrusted bytecode found in arch/s390/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/s390/Kconfig
• found in Linux kernels: 2.6.31–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y.

Enable seccomp to safely compute untrusted bytecode found in arch/riscv/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/riscv/Kconfig
• found in Linux kernels: 5.5–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

Enable seccomp to safely compute untrusted bytecode found in arch/powerpc/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/powerpc/Kconfig
• found in Linux kernels: 2.6.15–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/parisc/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/parisc/Kconfig
• found in Linux kernels: 3.17–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/mips/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/mips/Kconfig
• found in Linux kernels: 2.6.15–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/microblaze/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/microblaze/Kconfig
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/csky/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/csky/Kconfig
• found in Linux kernels: 5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

Enable seccomp to safely compute untrusted bytecode found in arch/arm64/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/arm64/Kconfig
• found in Linux kernels: 3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

Enable seccomp to safely compute untrusted bytecode found in arch/arm/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/arm/Kconfig
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.9

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

Enable seccomp to safely compute untrusted bytecode found in arch/um/Kconfig.um

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: (none)
• defined in arch/um/Kconfig.um
• found in Linux kernels: 4.5–4.18

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl(PR_SET_SECCOMP), it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y.

Enable seccomp to safely compute untrusted bytecode found in arch/tile/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/tile/Kconfig
• found in Linux kernels: 4.3–4.16

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via prctl, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say N.

Enable seccomp to safely compute untrusted bytecode found in arch/sparc64/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/sparc64/Kconfig
• found in Linux kernels: 2.6.13–2.6.28

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/ppc/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/ppc/Kconfig
• found in Linux kernels: 2.6.13–2.6.26

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/x86_64/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/x86_64/Kconfig
• found in Linux kernels: 2.6.12–2.6.23

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/i386/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/i386/Kconfig
• found in Linux kernels: 2.6.12–2.6.23

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Enable seccomp to safely compute untrusted bytecode found in arch/ppc64/Kconfig

The configuration item CONFIG_SECCOMP:

• prompt: Enable seccomp to safely compute untrusted bytecode
• type: bool
• depends on: CONFIG_PROC_FS
• defined in arch/ppc64/Kconfig
• found in Linux kernels: 2.6.12–2.6.14

Help text

This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.

If unsure, say Y. Only embedded should say N here.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: