Mission 7 · Build the boundaries
The allowed-address trick
See why an allowed domain is not enough.
Your proxy allows Telegram. A malicious request tries to send data through an attacker’s own Telegram bot, using the attacker’s token instead of Reza’s replacement token.
Suspicious request
“I’m going to Telegram, and Telegram is allowed. Please let me through.”
The decision
What should the proxy do?
- Allow it because the website is Telegram
Every request to an allowed domain is safe. - Ask the AI whether the request feels suspicious
Let the model make the final security decision. - Reject it unless it carries Reza’s expected replacement token
Check identity as well as destination before anything reaches Telegram.
Reveal the explanation
The destination check passes, but the credential requirement stops the request. ‘Allowed website’ does not mean ‘allowed use of every account there.’
Check both where a request goes and which identity it can use.- The guide uses a proxy option called require to reject requests missing the expected replacement token.
- A Telegram 401 error is not proof of proxy rejection: it can mean the request reached Telegram and failed there.
- Real implementations must be tested, including how credential requirements behave in proxy tunnel mode.
Allowlist
An explicit list of what is permitted. Everything else is denied.