You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Security implications of a runner activating a prebuilt environment #50
If a runner does not build and is handed a pre-built environment, it needs to activate it (for comparisons at least). That means it executes a shell command.
That has some security implications, as the shell command comes from the user.
This is not used anywhere currently; One place where a runner would want to activate an environment is UC-04 bx compare in the measurement mode, where bx compare would need to run the workload in two environments. This does not seem to be badly needed: gh-81 seems to adequately handle this use case with interleaved bx bench calls followed by a run-mode bx compare to pull the data from the store.
Activity
ev-br commentedon Oct 28, 2026
This is not used anywhere currently; One place where a runner would want to activate an environment is UC-04
bx comparein the measurement mode, wherebx comparewould need to run the workload in two environments. This does not seem to be badly needed: gh-81 seems to adequately handle this use case with interleavedbx benchcalls followed by a run-modebx compareto pull the data from the store.