Repository navigation
TEST 109
Offer the packager readiness receipts from a guest whose sshd lets an account other than root log in, from one that accepts a password, and from one with an authorized_keys file. Boot a lane instance whose client-key property is missing, and one whose property the guest can write. Run the lane with a run directory that its group can reach, with a run directory that already holds a key file, and against an instance whose host key differs from the box receipt's. In clean instances, create pb-workload or /run/projectbuddy-lane before the run, make a placed file differ from what the engine sent, and declare a candidate with a submodule. Then run a clean lane with one declared secret whose fetch and build steps try to write to /run/projectbuddy-lane, read the secrets file, and schedule a cron and an at job.
The packager refuses all three readiness receipts and writes no box receipt. Neither instance accepts a login. Each run refusal stops the run before the next step and before the workload starts. In the clean run, every probe and step runs with the workload account's user ID; its writes to /run/projectbuddy-lane and its reads of the secrets file fail; crontab and at refuse it; and the secret's value appears in no log, message, or evidence byte.