Registry: reject installer symlinks escaping plugin root #202

New issue

Closed

opened 2026-09-08 02:03:13 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:13 +00:00

Owner

Registry P0 follow-up.

The registry validates that plugins/<name>/tools/<name> exists and that install metadata agrees with its presence, but Path.is_file() follows symlinks. A canonical plugin root can therefore advertise an installer path that resolves outside the plugin root.

Acceptance:

deterministic RED for an external installer symlink;
installer path must resolve inside its plugin root before nix run / install.tool metadata is accepted;
canonical in-tree installers remain valid;
static/import-free validation;
full compatibility, nix flake check, and package builds green.

Registry P0 follow-up. The registry validates that `plugins/<name>/tools/<name>` exists and that install metadata agrees with its presence, but `Path.is_file()` follows symlinks. A canonical plugin root can therefore advertise an installer path that resolves outside the plugin root. Acceptance: - deterministic RED for an external installer symlink; - installer path must resolve inside its plugin root before `nix run` / install.tool metadata is accepted; - canonical in-tree installers remain valid; - static/import-free validation; - full compatibility, `nix flake check`, and package builds green.

nsaspy closed this issue

2026-09-08 02:03:13 +00:00

nsaspy referenced this issue

2026-09-08 02:17:36 +00:00

[WORKER] Providers+Home — SmartThings, calendar/comms and production integration hardening #55

nsaspy referenced this issue

2026-09-08 02:17:37 +00:00

[WORKER] Providers+Home — SmartThings, calendar/comms and production integration hardening #55

nsaspy referenced this issue

2026-09-08 02:17:37 +00:00

[WORKER] Providers+Home — SmartThings, calendar/comms and production integration hardening #55

nsaspy referenced this issue