BLAHAJ
/
has-writeup
10
2
Fork 0
Code Releases Activity

bytes away: note about ENABLE_TELEMETRY

This commit is contained in:
xenia 2020-05-26 02:14:47 -04:00
parent fb5ca39402
commit 8db550d150
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
satellite-bus/bytes-away/README.md
View File

@ -24,7 +24,8 @@ enormously complicated, so Docker can be used to automate the setup. We adapted
COSMOS Docker image, and created a script to configure COSMOS to connect to the CTF's satellite
instance automatically by writing the configuration file at
`cosmos/config/tools/cmd_tlm_server/cmd_tlm_server.txt`.
When COSMOS is successfully connected to the CTF instance it looks like this:
When COSMOS is successfully connected to the CTF instance it looks like this (no themes were
installed in the Docker container so it looks like Windows 95, I'm so sorry,)
![COSMOS main window](COSMOS.png)
COSMOS can be used to send commands with the Command Sender, and we can send for example a command
@ -56,7 +57,9 @@ bypassed.
Inspecting the structure of `KitToFlagPkt` shows that the flag is located at offset 12 and is (up
to) 200 bytes long. We created a Ruby script in the COSMOS Script Runner to execute PEEK_MEM
commands for each byte in the flag range, based on the command COSMOS outputs to the console when
running the command manually in the GUI.
running the command manually in the GUI. Note that in order for the function `KIT_TO_SendFlagPkt` to
be called at all, we must first run the ENABLE_TELEMETRY command even though we're not going to look
at any actual telemetry.
```ruby
12.upto(212) { |off|