wizardchen 49daad4602 feat(plugin): sandbox host plugins by default where Linux allows it ...

WEKNORA_PLUGIN_NETNS now defaults to auto. On Linux the plugin host probes
once, by starting the plugin-sandbox helper in a new user and network
namespace with nothing to run, whether the system lets it set the sandbox
up. If it does, every host plugin runs in its own network namespace; if it
does not (user namespaces refused by the kernel, AppArmor or a container's
seccomp profile), plugins run with the egress proxy only and one warning
says why and how to enable the sandbox. "1" still requires the sandbox and
fails the plugin without it, "0" turns it off, and other systems use the
proxy only. The standalone plugin host shares the same code.

Only programs that dispatch the helper are probed: WeKnora's main
registers it, so test binaries of other packages never start themselves.

The host manager reports per plugin whether its process is sandboxed or
only given the proxy.

2026-09-27 00:00:32 +08:00

..

bootstrap.go

refactor(api-keys): remove API key reset endpoint and update documentation

2026-07-07 12:00:13 +08:00

listen.go

feat: add server listening functionality with retry mechanism and platform-specific shutdown signal handling for improved robustness

2026-04-11 19:09:25 +08:00

main.go

feat(plugin): standalone plugin hosts with Redis discovery

2026-09-26 10:19:25 +08:00

plugin_host.go

feat(plugin): sandbox host plugins by default where Linux allows it

2026-09-27 00:00:32 +08:00

signals_unix.go

feat: add server listening functionality with retry mechanism and platform-specific shutdown signal handling for improved robustness

2026-04-11 19:09:25 +08:00

signals_windows.go

feat: add server listening functionality with retry mechanism and platform-specific shutdown signal handling for improved robustness

2026-04-11 19:09:25 +08:00