The lookup table for syscall names is already present. A JSON adaptor is needed for the NativeRule struct. The seccomp overrides are already removed from hst as part of v0.3.x.
When applying the custom filter, internal/app must ensure it does not reduce protection to the kernel. It might be sufficient to append custom filter rules to generated (preset) rules.
The lookup table for syscall names is already present. A JSON adaptor is needed for the `NativeRule` struct. The seccomp overrides are already removed from `hst` as part of v0.3.x.
When applying the custom filter, `internal/app` must ensure it does not reduce protection to the kernel. It might be sufficient to append custom filter rules to generated (preset) rules.
The underlying seccomp and std package now supports this to the extent of not requiring breaking changes to the exported API. Removing this from v0.3.0 as integrating this into hst will not break API.
The underlying `seccomp` and `std` package now supports this to the extent of not requiring breaking changes to the exported API. Removing this from v0.3.0 as integrating this into `hst` will not break API.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The lookup table for syscall names is already present. A JSON adaptor is needed for the
NativeRulestruct. The seccomp overrides are already removed fromhstas part of v0.3.x.When applying the custom filter,
internal/appmust ensure it does not reduce protection to the kernel. It might be sufficient to append custom filter rules to generated (preset) rules.The underlying
seccompandstdpackage now supports this to the extent of not requiring breaking changes to the exported API. Removing this from v0.3.0 as integrating this intohstwill not break API.This should be considered, alongside cleaning up seccomp-related API in
v0.4.