ig-ctf-solutions/write-ups-challenges-2022-2023
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
main
write-ups-challenges-2022-2023/corrupted-encryption
History
Robbe De Greef 0ac8165900 initial commit
2022-11-24 22:59:22 +01:00
..
app initial commit 2022-11-24 22:59:22 +01:00
dist-newstyle initial commit 2022-11-24 22:59:22 +01:00
CHANGELOG.md initial commit 2022-11-24 22:59:22 +01:00
corrupted-encryption.cabal initial commit 2022-11-24 22:59:22 +01:00
ctf flag (CONFLICTED COPY 2022-07-12) initial commit 2022-11-24 22:59:22 +01:00
encryptor.hs initial commit 2022-11-24 22:59:22 +01:00
original_gimped.jpg initial commit 2022-11-24 22:59:22 +01:00
original_gimped.xcf initial commit 2022-11-24 22:59:22 +01:00
original.jpg initial commit 2022-11-24 22:59:22 +01:00
output.jpg initial commit 2022-11-24 22:59:22 +01:00
README.md initial commit 2022-11-24 22:59:22 +01:00
SOLUTION.md initial commit 2022-11-24 22:59:22 +01:00

README.md

Corrupted Encryption

Text

I'm not much for this competitive hacking, so if I could I would have just given you the flag for this challenge. The problem is that the file on which I kept the flag was encrypted, but because of some syncing issues with my cloud, the encryption key got lost and the file can no longer be decrypted. Luckily I backed up the encryption key... but that backup is situated in the file itself...

The best course of action you can take now is to maybe figure out what the file type was and to go from there...

Oh, also, yes stupid me added an additional layer of encoding for the flag so you'll have to break through that too :)

Notice: There is a secret second flag hidden somewhere :o

Files

Participants get the ctf flag (CONFLICTED COPY 2022-07-12) provided, nothing else.

How to Deploy

N/A