8000 T131 — Choose each key's store on Linux and start the proxy there · Issue #3327 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

T131 — Choose each key's store on Linux and start the proxy there #3327

Closed

Description

@norrietaylor

Task

slice size difficulty model who estimated lines
Linux hosts hold the proxy's keys L needs care strongest an agent 720 (360 code, 360 tests)

On Linux, bep starts, keeps each key in the store it was generated in, and refuses with the role and the next step when a key is missing or its store cannot be read.

Covers:

  • BEP-088
  • BEP-089

Layers:

  • store:
    • crates/bep/src/linux_store.rs (new): a key store over the TPM store and the Secret Service store that looks up each role in every store, generates a missing key in the TPM where the TPM creates and loads it and otherwise in Secret Service, never generates a role that another store holds, and reports a store it cannot read
    • crates/bep/src/lib.rs: declares the linux_store module for Linux targets
    • crates/bep/src/keys.rs: load_with refuses a missing role without naming the replacement while a store cannot be read; custody is unchanged, because SecretServiceKey::exportable() returns false and a release build holds a Secret Service key (arch ruling 1238)
    • cargo nextest run -p bep linux_key_store_is_the_tpm_where_usable_else_secret_service
    • cargo nextest run -p bep no_tpm_and_no_secret_service_refuses_start
    • cargo nextest run -p bep a_held_key_is_never_moved_to_another_store
    • cargo nextest run -p bep a_missing_role_key_refuses_start_and_names_replacement
    • cargo nextest run -p bep a_missing_role_with_an_unreadable_store_refuses_start_and_keeps_the_key
  • binary:
    • crates/bep/src/main.rs: on Linux, run takes the Linux key store in place of the "bep runs only on macOS" refusal, for bep, bep serve and bep --replace-key
    • cargo nextest run -p bep linux_start_runs_on_the_linux_key_store

Waits on:

Plan block
### T131 — Choose each key's store on Linux and start the proxy there
  slice: S18
  kind: task
  covers: BEP-088, BEP-089
  size: L
  est: 360 code, 360 tests
  executor: agent
  difficulty: needs care
  model: strongest
  diagnostics: the refusals print to the person who started `bep`, pinned by their tests: "The proxy did not start: this host has no usable TPM and no unlocked Secret Service keyring, so the proxy has nowhere to keep its keys." when neither store can generate a key; "The proxy did not start: no key store it can read holds the proxy's <role> key, and <Secret Service is locked|Secret Service cannot be reached|the TPM cannot be reached>. The key may be there, so it is kept." when a store cannot be read; and "No key store on this host holds the proxy's <role> key. Run `bep --replace-key <role>` to make a new one. Boxes created before then must be re-created." when every store is readable; `bep` no longer prints "bep runs only on macOS" on Linux
  observability: `bep` logs, at each start on Linux, one line per role with the store that holds its key or `store=none`, and one line when a first start chooses a store, with the reason the TPM was not usable when it was not
  layers:
    - store:
      - crates/bep/src/linux_store.rs (new): a key store over the TPM store and the Secret Service store that looks up each role in every store, generates a missing key in the TPM where the TPM creates and loads it and otherwise in Secret Service, never generates a role that another store holds, and reports a store it cannot read
      - crates/bep/src/lib.rs: declares the `linux_store` module for Linux targets
      - crates/bep/src/keys.rs: `load_with` refuses a missing role without naming the replacement while a store cannot be read; `custody` is unchanged, because `SecretServiceKey::exportable()` returns `false` and a release build holds a Secret Service key (arch ruling 1238)
      test: cargo nextest run -p bep linux_key_store_is_the_tpm_where_usable_else_secret_service
      test: cargo nextest run -p bep no_tpm_and_no_secret_service_refuses_start
      test: cargo nextest run -p bep a_held_key_is_never_moved_to_another_store
      test: cargo nextest run -p bep a_missing_role_key_refuses_start_and_names_replacement
      test: cargo nextest run -p bep a_missing_role_with_an_unreadable_store_refuses_start_and_keeps_the_key
    - binary:
      - crates/bep/src/main.rs: on Linux, `run` takes the Linux key store in place of the "bep runs only on macOS" refusal, for `bep`, `bep serve` and `bep --replace-key`
      test: cargo nextest run -p bep linux_start_runs_on_the_linux_key_store
  produces:
    - crates/bep/src/linux_store.rs
  consumes:
    - crates/bep/src/tpm.rs
    - crates/bep/src/secret_service.rs
  proof: On Linux, `bep` starts, keeps each key in the store it was generated in, and refuses with the role and the next step when a key is missing or its store cannot be read.
  depends on:
    - blocked by #3324
    - blocked by #3326
    - blocked by #3325

Activity

  1. added
    kind:taskA task the plan skill rendered; the body carries ## Task
    size:L500 to 900 net lines; one PR, and the ceiling
    model:strongestThe strongest model available: unknown ground, or large work that needs care
    on Nov 12, 2026
  2. minimal-foundry commented on Nov 14, 2026

    @minimal-foundry
    Contributor

    Done. #3418 merged.

    branch agent/3327-choose-each-key-s-store-on-linux-and-start-the-p · epic #1501 · PR #3418

    round outcome job
    1 pushed 8e9628ce
    2 pushed 4c38afd6
    3 pushed b1931125
    4 pushed 55230827

    Updated 2026-11-14T06:48:10.835Z.

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

    kind:taskA task the plan skill rendered; the body carries ## Taskmodel:strongestThe strongest model available: unknown ground, or large work that needs caresize:L500 to 900 net lines; one PR, and the ceiling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0