Following on from Opabina Regalis - Token Fetch, can you get access to the
Listening on port 13001 on
This challenge also uses protocol buffers. We’re using full duplex sockets to act as both a client and a server on the same connection. When we first connect, we are sent a request to
/protected/not-secret. The goal is to get the server to send us an authenticated request to
/protected/secret, so that we can send an identical request right back and get an authenticated response.
Initial request from server:
The hash used in Digest auth includes the request URI. If the server gives us a hash for
/protected/not-secret, it won’t authorize us to
/protected/secret. We’ll respond with a 302 redirect response. The server will make another request, this time for
Now we make our own request to
/protected/secret to get the WWW-Authenticate challenge header.
Send this exact response at the server (responding to its
/protected/secret) and we should have a valid Authorization header.
Send the exact same request back at the server, and it will auth us.