Read the marks
You solve it by naming the closed account that went on reading after its close, and the time it first did.
- You start with
- The line's accounts export and its access log.
- In scope
- Your session's address, nothing else.
- You need
- curl or another HTTP client. A spreadsheet or a short script helps with the export and the log.
The Silt cache line, whose two records came in from the margin and do not agree.
A name struck from the roll still reads against the line. Until a Finder calls it, the line's count carries an entry no bird can stand behind.
The flag looks like duck{…}, with 32 hex characters inside, and the reader answers a right finding with it. It refuses a wrong one, and after three it locks the finding for the session.
Read the restShow less
Session
Your own copy, with flags made for it alone. On Free it runs up to 1 hour, from 3 lab hours a week.
Ask Nester when you're stuck.
It knows the brief and how your session stands. It answers with a question or an idea, never the answer, and it never sees your flags.
Your work
Flag 1
Counts only in your own session
Writeup
Opens once you find a flag
Hints, building
One at a time, when you ask.
Writeups, locked
Open once you clear it.
Source, building
Run it yourself, off the record.
This labWhat it teaches, how big a session is, and how hard it felt.
- What it teaches
- hidden until you clear it
- A session
- 1 service
- How hard it felt
- , building