Add support for different profile builds
- Vorherrschende Sprache
- C
- Sterne
- 178
- Forks
- 12
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Currently we are generating just one type of Seccomp profile with the `build` command.
The idea here is to provide the ability to configure your own profile based on your needs.
Eg. You might want to generate a less strict profile which can allow the logging of missing syscalls.
```json
{
"defaultAction": "SCMP_ACT_LOG",
"architectures": [
"SCMP_ARCH_X86_64",
"SCMP_ARCH_X86",
"SCMP_ARCH_X32"
],
"syscalls": [
{
"names": [
"arch_prctl",
"sched_yield",
"futex",
"write",
"mmap",
"exit_group",
"madvise",
"rt_sigprocmask",
"getpid",
"gettid",
"tgkill",
"rt_sigaction",
"read",
"getpgrp"
],
"action": "SCMP_ACT_ALLOW"
},
{
"names": [
"add_key",
"keyctl",
"ptrace"
],
"action": "SCMP_ACT_ERRNO"
}
]
}
```
Note that there might be more examples like the one above. For this reason I was thinking to add a flag on the `build` command, to allow the user of specifying the kind of profile which more fits his needs.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.