A secret store releases nothing until the caller authenticates, so what must already exist on a machine before its first fetch?

## The recursion, stated exactly A secret store is a running service, not a file: it answers a request only after the caller has proved who it is. That property is the reason to run one. It is also the reason a new machine cannot start empty. Before any value comes back, the machine must satisfy the store's authentication step, which means **something the store already accepts must exist on that machine, or be reachable from it, before the first fetch**. That something is the *bootstrap credential*, or the first secret. You need a credential to get credentials. This is not a defect in any one store. Every store has it, because the alternative — a store that hands a value to a caller it has not identified — is not a store. ## What actually happens at a restart Interviewers ask this because candidates describe the store as though the problem vanished. Walk the sequence instead: 1. The machine boots and the process starts holding no values. 2. The process presents whatever the store accepts as proof of who it is. 3. The store checks that proof, then decides what this caller is allowed to read. 4. The values come back over the connection and are used. 5. The machine restarts next week and step 2 happens again, unattended, with nobody at a terminal. Step 2 is the bootstrap problem, and it recurs at every restart rather than only at install. That is why *we set it up once* is not an answer. ## The three shapes the first credential takes | Shape | What sits on the machine | What it costs | |---|---|---| | A long-lived value placed once | a credential-shaped string that never changes | the exposure the store was meant to remove, now guarding everything the store will release to it | | A value accepted once, in a short window | nothing once the exchange completes | something trusted must hand it over at the right moment, and must be protected in turn | | No carried value at all | nothing | trust moves to the platform that vouches for the workload and to the store's rule about what it accepts | The first shape is what most estates actually run, and an honest answer says so rather than describing the ideal. The second is where most of the improvement is available without changing anything about the platform. The third is a separate subject — what a platform-signed identity document proves and what it does not — and knowing the route exists is as far as this question goes. ## Why the delivery shape is not the answer A weak answer stops at where the value is presented to the process. That is a delivery decision and a different subject. The properties that decide whether a first credential is tolerable are these: - **Lifetime.** Does a copy stop working on its own, and when? - **Redemption count.** May it be presented more than once, or exactly once? - **Scope.** Does it grant a read of everything the machine may see, or only the right to obtain a proper identity? - **Uniqueness.** Is it this machine's value, or the fleet's? - **Provenance.** Can anyone say who placed it there and on what date? A long random string scores well on guessing and badly on every one of those. Guessing is not the threat model for a value sitting in a file on a machine several people can reach; **copying is**, and length does nothing against copying. ## The strongest version of the answer Someone who has wired this says three things. First, the first credential always exists in some form, so the design question is only its lifetime, its scope and who delivers it. Second, the failure mode of the common arrangement — a value placed at build time and never touched — is not that it can be guessed, but that copies of it accumulate quietly and none of them expires. Third, the improvement available without changing the platform is to make the first credential worth almost nothing: unique to the machine, valid for minutes, accepted exactly once, and carrying only the right to obtain a real identity rather than the right to read stored values. Someone who has not wired it says the store took the secrets off the machine. Asking what the machine presents when it restarts unattended brings the real answer out immediately.