Fix crapto writeup

content/writeups/dragonsec2022/crapto.md → content/writeups/dragonsec2022/crapto/index.md

@@ -22,7 +22,7 @@ We have `keyfob.trace`, which is a log file. Firstly, we saw a `rfid` challenge
 
 The `keyfoab.trace` file is the result of some data generated by a keyfob, a small handheld remote control device that controls a remote keyless entry system.
 
-![key-fob.jpg](https://wiki-ulisse.fuo.fi/ctf/dragonsec-2022/crapto/key-fob.jpg)
+![key-fob.jpg](key-fob.jpg)
 
 So how can we read this special file? We searched some hardware tools for RFID security analysis and research, and we found out Proxmark3 was what we needed.
 
@@ -34,11 +34,11 @@ With `trace list` a table is shown which gives timing information, the src of th
 
 _By accident_ we discovered `trace list 2` gives a better help:
 
-![](/ctf/dragonsec-2022/crapto/dodo-trace.png)
+![](dodo-trace.png)
 
 Following the challenge title, we tried `trace list mf 1` in order to decrypt crypto1, an unsafe encryption algorithm (stream cipher) and authentication protocol created by NXP Semiconductors for its MIFARE Classic RFID contactless smart cards.
 
-![](/ctf/dragonsec-2022/crapto/crapto-solution.png)
+![](crapto-solution.png)
 
 We got the flag: