HackBlue

Labs / Secrets in Git

A deploy token in the CI workflow file

The deploy workflow now reads its token from repository secrets, but an earlier version had it inline. Follow the history of one file to find when it was added and by whom.

  • Terminal mission
  • Beginner
  • 4 objectives
  • 0 of 4 solved

What you’re looking at

The deploy workflow now reads its token from repository secrets, but an earlier version had it inline. Follow the history of one file to find when it was added and by whom.

Your goal: Find when a deploy token was written into the workflow file, by whom, and where it works.

Briefing
the story: what happened and what evidence you were handed.
Terminal
the dark box. It is a pretend Linux shell that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
Walkthrough
the numbered path. Each step says what to type and what you should see. Hints open one at a time.
Answer boxes
under each question step. Type what you found and press Check.

Words you will meet

CI
continuous integration, the server that builds and tests code

Start with step 1 in the walkthrough. Every step says what to do and what you should see. The whole thing takes about 2 min to talk through.

Briefing

status-site is a public repository that deploys a status page. Someone noticed that the deploy workflow used to contain the hosting token in plain text before it was moved to repository secrets.

git log -p -- <path> shows every change to one file, oldest change last. A secret that was removed in a later commit is still in the earlier ones.

analyst@dev-laptop

dev-laptop · Secrets in Git

Type help for the command list and objectives for your tasks. Everything runs in this browser.

Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.

The whole walkthrough

Every step in order, written to be read aloud: 300 words, about 2 min. It gives away every answer, so try the steps first.