> For the complete documentation index, see [llms.txt](https://picoctf2019.haydenhousen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://picoctf2019.haydenhousen.com/forensics/whitepages.md). # WhitePages ## Problem > I stopped using YellowPages and moved onto WhitePages... but the page they gave me is all blank! * [TXT File](https://github.com/HHousen/PicoCTF-2019/tree/24b0981c72638c12f9a8572f81e1abbcf8de306d/Forensics/WhitePages/whitepages.txt) ## Solution 1. If we inspect the file using a HEX editor, we can see that there are two types of whitespaces: ```bash $ xxd whitepages.txt | head 00000000: e280 83e2 8083 e280 83e2 8083 20e2 8083 ............ ... 00000010: 20e2 8083 e280 83e2 8083 e280 83e2 8083 ............... 00000020: 20e2 8083 e280 8320 e280 83e2 8083 e280 ...... ........ 00000030: 83e2 8083 20e2 8083 e280 8320 e280 8320 .... ...... ... 00000040: 2020 e280 83e2 8083 e280 83e2 8083 e280 .............. 00000050: 8320 20e2 8083 20e2 8083 e280 8320 e280 . ... ...... .. 00000060: 8320 20e2 8083 e280 83e2 8083 2020 e280 . ......... .. 00000070: 8320 20e2 8083 2020 2020 e280 8320 e280 . ... ... .. 00000080: 83e2 8083 e280 83e2 8083 2020 e280 8320 .......... ... 00000090: e280 8320 e280 8320 e280 83e2 8083 e280 ... ... ........ ``` 2. We have the standard space (`0x20`), and the Unicode EM SPACE (`0xE2 0x80 0x83`). Since we have only two options, let's try to treat them as binary. 3. Run the [script.py](https://github.com/HHousen/PicoCTF-2019/tree/24b0981c72638c12f9a8572f81e1abbcf8de306d/Forensics/WhitePages/script.py) (which is commented) and get the flag. ### Flag `picoCTF{not_all_spaces_are_created_equal_f71be4d2457dc2d068e8b1e7a51ed39a}` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://picoctf2019.haydenhousen.com/forensics/whitepages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.