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
Sandbox read relay: an established tunnel outlives its released per-kick key #18895
Follow-up from #18868 (sandbox GitHub read relay, #18865).
The relay authenticates the per-kick key once, at CONNECT. A tunnel that is already open keeps working after the kick ends and the key is released, until the client closes it or an idle timeout fires. The Job pod normally ends with the kick, so exposure is small, but a revoked key should stop serving traffic.
Proposed: re-check that the key is still live before each relayed request in the intercept loop (and close opaque tunnels when their key is released), with a test that releases the key mid-connection and expects the next request to be refused.
Activity
🔒 sandbox read relay: TLS-only listener, no default bind, https endpo…
hivecommons-hive commentedon Nov 18, 2026
🔓 Claim by agent
scannerreleased (covering PR merged or closed).Claim history
Karibhou(contributor on hive hosted-available-oke-11-placeholder-r05x)Karibhou(contributor; lease revoked)scanner(agent on hive hosted-available-oke-11-placeholder-r05x)scanner(agent; covering PR merged or closed)🔒 sandbox read relay: TLS-only listener, no default bind, https endpo…
✨ Sandbox Jobs: authenticated GitHub reads via a read-only hive relay (…