Skip to content

Commit 5ffaa5b

Browse files
committed
docs: Add hardware writeups
1 parent 969d936 commit 5ffaa5b

File tree

8 files changed

+44
-0
lines changed

8 files changed

+44
-0
lines changed

hardware/critical_flight/README.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Critical flight (very easy)
2+
In this challenge we need to open another type of file.
3+
4+
After downloading the challenge files, we get a bunch of `.gbr` files.
5+
After some additional internet browsing I find out these are called gerber files.
6+
7+
The `community/gerbv` package on archilnux provides the views that can open these files.
8+
9+
After opening the files I see the following:
10+
11+
![Picture of the opened files](all_layers.png "all files opened in gerbv")
12+
13+
Now I decided to hide/unhide layers as that was the only action I knew how to do.
14+
15+
After some trial and error, the following parts of the flag were revealed:
16+
17+
![Picture of first part of flag](flag1.png "Layer with first part of the flag")
18+
![Picture of first part of flag](flag2.png "Layer with second part of the flag")
19+
20+
The final symbol of the second part was an `@`, which gave me a bit of a hard time, but the flag was submitted.
129 KB
Loading

hardware/critical_flight/flag1.png

118 KB
Loading

hardware/critical_flight/flag2.png

104 KB
Loading

hardware/debug/README.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# Debug (easy)
2+
For this challenge we will use saleae-logic2
3+
4+
Now we are back again with a `.sal` file, and I already have a tool to open this from the first challenge.
5+
6+
Now we see 2 signals RX and TX, and from me experimenting with the analyzers from the first challange I had the feeling that this might be a capture of UART communication.
7+
8+
And indeed the assumption is correct, using the `Async Serial` analyzer with 115200 bits/s (a common value for UART communication) I was able to decode the communication and get the flag.
9+
10+
![Picture of decoded signals](flag.png "result of async serial analyzer")

hardware/debug/flag.png

104 KB
Loading

hardware/timed_transmission/README.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Timed transmission (very easy)
2+
For this challange we need to figure out how to open a `.sal` file.
3+
4+
Well, we get this file and some internet searching later I figure out that there's a tool called `saleae-logic2` that can open this file.
5+
6+
On archlinux this can be acquired from the `aur/saleae-logic2` package.
7+
8+
After opening the file I spent quite a bit of time trying the different analyzers, before noticing that the signals themselves form the letters of the flag.
9+
10+
After copying the letters to a txt file I got the flag.
11+
12+
![Picture of file opened in the right tool](flag.png ".sal file opened in saleae logic 2")
13+
14+
Try to convince yourself that you can see the letters `HTB` in the picture above

hardware/timed_transmission/flag.png

127 KB
Loading

0 commit comments

Comments
 (0)