Skip to content

Sandbox read relay: an established tunnel outlives its released per-kick key #18895

Closed

Description

@clubanderson

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.

Left out of #18868 by the owner's decision.

Activity

  1. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by agent scanner released (covering PR merged or closed).

    Claim history
    • 2026-11-18 04:44 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-18 04:53 UTC — released by Karibhou (contributor; lease revoked)
    • 2026-11-18 05:41 UTC — claimed by scanner (agent on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-18 07:21 UTC — released by scanner (agent; covering PR merged or closed)
  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions