commit 83827ad7f87c0f3a6977e19e9aafda2908e3a505 Author: Danhia Date: Fri Feb 18 00:20:57 2022 +0100 first commit diff --git a/README.md b/README.md new file mode 100644 index 0000000..e69de29 diff --git a/en/ancient_crypto.html b/en/ancient_crypto.html new file mode 100644 index 0000000..4821149 --- /dev/null +++ b/en/ancient_crypto.html @@ -0,0 +1,12 @@ +So, I've heard you're kinda new to cryptography ?
+
+Basically, in almost every challenge you'll be provided a ciphertext that will look mostly garbage to you, and your goal will be to recover the original message.
+Messages are usually encrypted with a well-known cipher, so first step would be to guess the cipher and do some research on how to break it.
+Here is a list of useful websites:
+- https://www.dcode.fr/en
+- https://gchq.github.io/CyberChef/
+- https://docs.python.org/3/ (because if you try to solve the crypto challenges in C it will be long and painful)
+
+The flag is the decrypted message put into 42CTF{}.
+Ex: 42CTF{Th1s_1s_a_Fl4g}
+Good luck ! \ No newline at end of file diff --git a/en/another_weird_magic.html b/en/another_weird_magic.html new file mode 100644 index 0000000..4696c62 --- /dev/null +++ b/en/another_weird_magic.html @@ -0,0 +1,7 @@ +I tried the same spells as you told me the first time but it didn't work!

+ +Do you think you can help me this time?

+ +
Hint
+ +You do not need to reverse the whole given LUA interpreter. \ No newline at end of file diff --git a/en/armored.html b/en/armored.html new file mode 100644 index 0000000..8004d55 --- /dev/null +++ b/en/armored.html @@ -0,0 +1,3 @@ +This binary pretends to be an unbreakable chest! I tried for hours but it still resists.

+ +Do you think you can discover its secret? \ No newline at end of file diff --git a/en/client_side.html b/en/client_side.html new file mode 100644 index 0000000..0570011 --- /dev/null +++ b/en/client_side.html @@ -0,0 +1,12 @@ +So, I've heard you're kinda new to web ?
+
+Basically, in every challenge you'll be provided a url and you'll need to hack your way through the website.
+First step is usually to look at the source code of the page, so you'll need to know a bit about html/css/javascript. It will be enough for this first challenge, so you can solve it now and come back to read the remaining later ;)

+ +Of course you'll also need some knowledge about languages you won't see the source code, mainly php and various languages related to databases (such as MySQL). After that, you'll have to exploit the vulnerabilities in the web page. For that, you'll need to identify the features provided by the website and do some research on the associated exploits.
+Here is some useful links to get you started:
+- https://developer.mozilla.org/en-US/docs/Tools
+- https://owasp.org/www-project-top-ten/
+- https://portswigger.net/burp
+
+Good luck ! \ No newline at end of file diff --git a/en/come_on.html b/en/come_on.html new file mode 100644 index 0000000..b212d80 --- /dev/null +++ b/en/come_on.html @@ -0,0 +1 @@ +Trust me, it's not that hard \ No newline at end of file diff --git a/en/contact_support.html b/en/contact_support.html new file mode 100644 index 0000000..99c7ced --- /dev/null +++ b/en/contact_support.html @@ -0,0 +1,13 @@ +Hi [REDACTED],

+ +I need your services.
+Last week, we infiltrated the network of the huge international bank [REDACTED].
+When analyzing the network traffic, our compromised workstation discovered a suspicious API thath seems to be the endpoint of a support application.
+Since we are listening the network, it was used only once. +I need you to recover the ticket content.

+ +We are forwarding all the requests to the API for you at challenges.42ctf.org:2001.

+ +Regards,

+ +[REDACTED]

\ No newline at end of file diff --git a/en/easy_peasy_lemon_squezzy.html b/en/easy_peasy_lemon_squezzy.html new file mode 100644 index 0000000..1d12f8a --- /dev/null +++ b/en/easy_peasy_lemon_squezzy.html @@ -0,0 +1 @@ +Don't look too far \ No newline at end of file diff --git a/en/f5_not_allowed.html b/en/f5_not_allowed.html new file mode 100644 index 0000000..65159b9 --- /dev/null +++ b/en/f5_not_allowed.html @@ -0,0 +1,40 @@ +So, I've heard you're kinda new to reverse-engineering ?
+
+Basically, in almost every challenge you'll be provided a binary hiding a secret.
+Your goal is generally to break the secret checking function in order to recover the flag.
+For this you'll need to understand the assembly code and write back the corresponding C code if you need to (or you can do it in real-time if you're not human).
+
+To make it easier, i'll give you the flag checking function only and your task will be to recover which input returns 1.
+I advise you to do some research about x86 ISA and x86 linux calling convention first.
+
+Good luck !
+
+
+
+0000000000001139 <check_secret>:
+    1139:       55                      push   rbp
+    113a:       48 89 e5                mov    rbp,rsp
+    113d:       48 89 7d e8             mov    QWORD PTR [rbp-0x18],rdi
+    1141:       48 8b 45 e8             mov    rax,QWORD PTR [rbp-0x18]
+    1145:       48 89 45 f8             mov    QWORD PTR [rbp-0x8],rax
+    1149:       48 8b 45 f8             mov    rax,QWORD PTR [rbp-0x8]
+    114d:       8b 00                   mov    eax,DWORD PTR [rax]
+    114f:       35 40 20 5b 7f          xor    eax,0x7f5b2040
+    1154:       89 45 f0                mov    DWORD PTR [rbp-0x10],eax
+    1157:       48 8b 45 f8             mov    rax,QWORD PTR [rbp-0x8]
+    115b:       48 83 c0 04             add    rax,0x4
+    115f:       8b 00                   mov    eax,DWORD PTR [rax]
+    1161:       35 53 23 59 76          xor    eax,0x76592353
+    1166:       89 45 f4                mov    DWORD PTR [rbp-0xc],eax
+    1169:       81 7d f0 37 13 37 13    cmp    DWORD PTR [rbp-0x10],0x13371337
+    1170:       75 10                   jne    1182 <check_secret+0x49>
+    1172:       81 7d f4 37 13 37 13    cmp    DWORD PTR [rbp-0xc],0x13371337
+    1179:       75 07                   jne    1182 <check_secret+0x49>
+    117b:       b8 01 00 00 00          mov    eax,0x1
+    1180:       eb 05                   jmp    1187 <check_secret+0x4e>
+    1182:       b8 00 00 00 00          mov    eax,0x0
+    1187:       5d                      pop    rbp
+    1188:       c3                      ret
+
+
+
\ No newline at end of file diff --git a/en/force_brute.html b/en/force_brute.html new file mode 100644 index 0000000..fac70da --- /dev/null +++ b/en/force_brute.html @@ -0,0 +1,18 @@ +Last night I was in a party at 42, chill, then after a few drinks, I managed to get the password of uncle Niel !!
+Well, he didn't want to give it to me directly but he sent me its MD5 hash saying that I will never crack it hu hu hu ...
+ +After a few investigations and a little forcing, I ended up knowing roughly its composition, here is the order:
+ - A number between 0 and 42
+ - One of the company he founded
+ - His rank in the top 50 of french fortunes
+ - The first name of a close member of his family.
+
+Every word/name begins with a capital letter. Let's make a wordlist and try !
+
+Here is the hash : 55d91e34650fd1a804cd94f5f39b34fb
+
+ +

Tips

+If you have more than 17 years of your life to lose, you can try to crack it with something else than a wordlist you generated.
+And yes, some values may change over the years, but it will not be a problem for this challenge.
+Here is the flag format: 42CTF{} \ No newline at end of file diff --git a/en/gallery.html b/en/gallery.html new file mode 100644 index 0000000..6227b79 --- /dev/null +++ b/en/gallery.html @@ -0,0 +1,6 @@ +Someone told us that 42ctf was not user-friendly, so we decided to add a gallery of users pics.
+It's a very simple gallery so we are pretty sure that nothing can go wrong.
+
+Don't hesitate to upload some .css though, front dev is a real job and it's definitely not mine (just joking, css won't help you on this challenge)

+ +Fuzzing tools such as dirbuster, dirsearch, gobuster, wfuzz (non-exhaustive list) are useless and forbidden. \ No newline at end of file diff --git a/en/gallery_v2.html b/en/gallery_v2.html new file mode 100644 index 0000000..cbc2a7c --- /dev/null +++ b/en/gallery_v2.html @@ -0,0 +1,4 @@ +Ok it seems like our previous gallery was insecure and some of you managed to hack it.
+But now there is nothing you can do, since I'm checking the type of every file you try to upload.
+So be nice and just provide some jpeg.
+(I'm disappointed that nobody uploaded css on the last challenge though, thus this gallery will be as ugly as the other one) \ No newline at end of file diff --git a/en/gotcha.html b/en/gotcha.html new file mode 100644 index 0000000..a4242f7 --- /dev/null +++ b/en/gotcha.html @@ -0,0 +1,3 @@ +Don't try to overwrite the saved instruction pointer, you can't đź‘€
+
+When you'll be ready: nc challenges.42ctf.org 3003
\ No newline at end of file diff --git a/en/identified_author.html b/en/identified_author.html new file mode 100644 index 0000000..9769734 --- /dev/null +++ b/en/identified_author.html @@ -0,0 +1,9 @@ +
Hill Cipher - Known plaintext
+ +Our spy has intercepted this message. It contains the meeting place of double agents working for our enemies. Unfortunately, we haven't decrypted it yet.

+ +The only hint we have is the name of the author that our spy has been able to identify: BROWN.

+ +Good luck.

+ +PS: the flag is 42CTF{THEPLACEOFMEETING} \ No newline at end of file diff --git a/en/in_stack_we_trust.html b/en/in_stack_we_trust.html new file mode 100644 index 0000000..03f4f0b --- /dev/null +++ b/en/in_stack_we_trust.html @@ -0,0 +1 @@ +Be careful! Sometimes, the stack is not reliable as we thought... \ No newline at end of file diff --git a/en/its_all_here.html b/en/its_all_here.html new file mode 100644 index 0000000..a8798af --- /dev/null +++ b/en/its_all_here.html @@ -0,0 +1,8 @@ +So, I've heard you kinda new to steganography ?
+
+Basically, in every challenge you'll be provided a file and first step will be te determine its type, because the next steps won't be the same depending on wether you got a jpeg, a pdf or a mp3. The "file" command could be very helpful.
+Once you've got this info, you'll need to do some research about how to hide messages in this particular file type. Also keep in mind for later challenges that some files can be valid for several types, and that it can be worth to try to unzip files that don't look like zip files. Besides, steganography is traditionaly the art of hiding information into images, so sometimes you'll just have to look very carefully to find the flag.
+Here is a useful tool to get you started: https://github.com/exiftool/exiftool.
+Doing some research about image metadata can be a good beginning too.
+
+Good luck ! \ No newline at end of file diff --git a/en/my_little_pwn.html b/en/my_little_pwn.html new file mode 100644 index 0000000..d52ec93 --- /dev/null +++ b/en/my_little_pwn.html @@ -0,0 +1,12 @@ +So, I've heard you're kinda new to pwn ?
+
+Basically, in almost every challenge you'll be provided a binary and an access to our server on which the binary is listening to you. Sometimes you'll also be provided the source code (that's the case for this challenge).
+Your goal is generally to read the content of a file "flag.txt" on the server.
+For this you'll need to exploit vulnerabilities of the given binary. So the first step would be to identify those vulnerabilities, and then to do some research to find out how to exploit them.
+The binary is given to you so that you can try your exploits on your local machine (which has to be running on linux, otherwise you won't be able to run the binary).
+I advise you to do some research about "buffer overflow" to get you started.
+
+When you'll be ready: nc challenges.42ctf.org 3002
+Good luck !
+
+PS: don't forget to download the files \ No newline at end of file diff --git a/en/norm_error.html b/en/norm_error.html new file mode 100644 index 0000000..9ffe580 --- /dev/null +++ b/en/norm_error.html @@ -0,0 +1,11 @@ +Beware, 42 students.
+Norminette v3 is coming.

+ +Luckily for you, here at 42ctf we have the solution.
+Solve this challenge and you'll never have to worry anymore about norm errors.

+ +TRAILER

+ +----------------------------------

+ +with the participation of louveet and reveng \ No newline at end of file diff --git a/en/norminet_osint.html b/en/norminet_osint.html new file mode 100644 index 0000000..554c117 --- /dev/null +++ b/en/norminet_osint.html @@ -0,0 +1,8 @@ +Oh no !
+I refused to gave the tuna of my sandwich to Norminet and he stole us a flag !!
+Do what you want but I give up, this cat is way too much violent and he's scaring me !
+I let you with this picture, that's the only clue we have ...
+
+### Tips
+
+You will need to put the flag inside 42CTF{} before submitting it. \ No newline at end of file diff --git a/en/pas_les_bases.html b/en/pas_les_bases.html new file mode 100644 index 0000000..eee01ce --- /dev/null +++ b/en/pas_les_bases.html @@ -0,0 +1,4 @@ +Sorry I can't translate the title of this challenge because it's a reference to a french song.

+ + +Anyway, you need to begin somewhere, so let's begin with something very basic. \ No newline at end of file diff --git a/en/point_par_point.html b/en/point_par_point.html new file mode 100644 index 0000000..e7bf8aa --- /dev/null +++ b/en/point_par_point.html @@ -0,0 +1 @@ +A piece of advice to succeed in steganography: be punctillous. \ No newline at end of file diff --git a/en/recycling.html b/en/recycling.html new file mode 100644 index 0000000..5987cce --- /dev/null +++ b/en/recycling.html @@ -0,0 +1,3 @@ +They told us to discard our keys but we find it more eco-friendly to reuse them.

+ +Hint: The flag is inside 42CTF{} and messages are in english. \ No newline at end of file diff --git a/en/silkway_v1.html b/en/silkway_v1.html new file mode 100644 index 0000000..98d9bf0 --- /dev/null +++ b/en/silkway_v1.html @@ -0,0 +1,3 @@ +The new hackers of deep dark net have developped a new market, based on blockchain, they say it's ultra secured. Your mission is to empty their bitcoin wallet.

+ +Fuzzing tools such as dirbuster, dirsearch, gobuster, wfuzz (non-exhaustive list) are useless and forbidden. \ No newline at end of file diff --git a/en/skynout.html b/en/skynout.html new file mode 100644 index 0000000..3e0d8b2 --- /dev/null +++ b/en/skynout.html @@ -0,0 +1,4 @@ +You're in a hurry.
+In its madness, 42CTF administration decided to rule the world by using their nukes management system: Skynout.
+You've managed to get into the server room of Skynout, but the computer asks you for a password.
+The fate of the world is in your hands. \ No newline at end of file diff --git a/en/some_weird_magic.html b/en/some_weird_magic.html new file mode 100644 index 0000000..289ed3e --- /dev/null +++ b/en/some_weird_magic.html @@ -0,0 +1,5 @@ +This is weird, I never encountered this kind of magic before...

+ +My magic teacher told me about "byte code" but i don't know what it is.

+ +Could you help me? \ No newline at end of file diff --git a/en/the_answer.html b/en/the_answer.html new file mode 100644 index 0000000..5551e27 --- /dev/null +++ b/en/the_answer.html @@ -0,0 +1,3 @@ +Alright, so now it's time to put in practice what you've learnt in the intro challenge.
+Nothing new, don't forget to download the files and everything will be fine.
+When you'll be ready: nc challenges.42ctf.org 3001 \ No newline at end of file diff --git a/en/the_fault_in_our_DES.html b/en/the_fault_in_our_DES.html new file mode 100644 index 0000000..dfdfab7 --- /dev/null +++ b/en/the_fault_in_our_DES.html @@ -0,0 +1,8 @@ +Our engineer did a differential fautl analysis on a smart card - or rather he began the attack.
+He went on vacation before the data analysis, so now it's your task, first year intern.

+We'll give you the plaintext, the ciphertext, and 32 faulted ciphertexts.
+You need to recover the 64 bits key and to submit it in hexadecimal inside the 42CTF{} tag.

+ +Example : 42CTF{1234567890ABCDEF}
+
+Good luck.
\ No newline at end of file diff --git a/en/triple_word.html b/en/triple_word.html new file mode 100644 index 0000000..f44f96f --- /dev/null +++ b/en/triple_word.html @@ -0,0 +1,3 @@ +We've intercepted three messages encrypted with three different public keys. It seems that all the messages have been sent simultaneously.

+ +There's probably very important information hidden in one of them. \ No newline at end of file diff --git a/en/very_short_crypto.html b/en/very_short_crypto.html new file mode 100644 index 0000000..b10e112 --- /dev/null +++ b/en/very_short_crypto.html @@ -0,0 +1,5 @@ +We've intercepted this encrypted message and the corresponding public key.

+ +We think it's a password.

+ +PS: the flag is 42CTF{password} (and it's case sensitive) \ No newline at end of file diff --git a/en/we_need_a_pattern.html b/en/we_need_a_pattern.html new file mode 100644 index 0000000..dedabd0 --- /dev/null +++ b/en/we_need_a_pattern.html @@ -0,0 +1,7 @@ +We've intercepted a text encrypted with an unknown cipher.

+ +We think that it's written in english and that it contains very important information.

+ +
Hint
+ +You need to put the flag inside 42CTF{} and to uppercase. \ No newline at end of file diff --git a/fr/ancient_crypto.html b/fr/ancient_crypto.html new file mode 100644 index 0000000..86647c6 --- /dev/null +++ b/fr/ancient_crypto.html @@ -0,0 +1,12 @@ +Alors, il paraît que tu débutes en cryptographie ?
+
+En fait, dans presque tous les challenges, on te fournira un texte chiffré qui ne ressemblera pas à grand chose pour toi, et ton objectif sera de retrouver le message original. +Les messages sont généralement chiffrés à l'aide d'un algorithme bien connu. La première étape consiste donc à deviner l'algorithme et à faire des recherches sur la façon de le casser. +Voici une liste de sites Web utiles :
+- https://www.dcode.fr/en
+- https://gchq.github.io/CyberChef/
+- https://docs.python.org/3/ (parce que si tu essayes de résoudre les challenges crypto en C ce sera long et douloureux)
+
+Le flag est le message déchiffré mis dans 42CTF{}.
+Ex: 42CTF{Th1s_1s_a_Fl4g}
+Bonne chance ! \ No newline at end of file diff --git a/fr/client_side.html b/fr/client_side.html new file mode 100644 index 0000000..8479a54 --- /dev/null +++ b/fr/client_side.html @@ -0,0 +1,15 @@ +Alors, j'ai entendu que tu débutais en web ?

+ +En fait, dans tous les challenges on te fournira une url, et tu devras hacker ce site internet.
+La première chose à faire est en général de regarder le code source de la page, donc tu auras besoin de connaitre deux-trois trucs en html/css voire en javascript. Ça suffira pour ce premier challenge, donc tu peux dès à présent le résoudre et revenir lire la suite plus tard ;)

+ +Pour les autres, tu auras également besoin de connaissances dans des langages dont tu ne verras pas le code source, principalement du php, ainsi que pas mal de langages liés aux base de données (comme MySQL).
+Ensuite, tu devrais exploiter les vulnérabilités de la page web. Pour ça, il te faudra identifier les fonctionnalités du site et faire quelques recherches sur comment les exploiter.

+ +Quelques liens utiles pour démarrer : +- https://developer.mozilla.org/en-US/docs/Tools
+- https://owasp.org/www-project-top-ten/
+- https://portswigger.net/burp
+
+ +Bon courage ! \ No newline at end of file diff --git a/fr/come_on.html b/fr/come_on.html new file mode 100644 index 0000000..d17db69 --- /dev/null +++ b/fr/come_on.html @@ -0,0 +1 @@ +Fais moi confiance, ce n'est pas si difficile \ No newline at end of file diff --git a/fr/easy_peasy_lemon_squezzy.html b/fr/easy_peasy_lemon_squezzy.html new file mode 100644 index 0000000..d4b8282 --- /dev/null +++ b/fr/easy_peasy_lemon_squezzy.html @@ -0,0 +1 @@ +Ne regarde pas trop loin \ No newline at end of file diff --git a/fr/force_brute.html b/fr/force_brute.html new file mode 100644 index 0000000..a58b84b --- /dev/null +++ b/fr/force_brute.html @@ -0,0 +1,17 @@ +Hier j'étais en soirée 42, tranquille, puis après quelques verres, j'ai réussi à récupérer le mot de passe de tonton Niel !!
+Bon il a pas voulu me le donner directement mais il m'a envoyé son hash en MD5 me disant que j'arriverais jamais à le craquer héhéhé...
+Après quelques investigations et un peu de forcing, j'ai fini par vaguement connaitre sa composition, la voici dans l'ordre :
+ - Un nombre compris entre 0 et 42
+ - Une des boites dont il est le fondateur
+ - Son classement dans le top 50 des fortunes françaises
+ - Le prenom d'un membre proche de sa famille
+
+Chaque mot/nom commence par une majuscule. Plus qu'Ă  faire une wordlist et essayer !
+
+Voici le hash : 55d91e34650fd1a804cd94f5f39b34fb
+
+

Tips

+
+Si t'as plus de 17 ans de ta vie à perdre, tu peux essayer de le cracker autrement qu'en utilisant une wordlist que t'as généré.
+Et oui, certaines valeurs peuvent changer au cours du temps mais ça ne te posera pas de problèmes pour ce challenge.
+Le flag est sous le format : 42CTF{} \ No newline at end of file diff --git a/fr/gotcha.html b/fr/gotcha.html new file mode 100644 index 0000000..8c9ef8c --- /dev/null +++ b/fr/gotcha.html @@ -0,0 +1,3 @@ +N'essaye pas de réécrire le pointer d'instruction sauvé, tu ne peux pas 👀
+
+Quand tu seras prĂŞt : nc challenges.42ctf.org 3003
\ No newline at end of file diff --git a/fr/its_all_here.html b/fr/its_all_here.html new file mode 100644 index 0000000..4eeb655 --- /dev/null +++ b/fr/its_all_here.html @@ -0,0 +1,9 @@ +Alors, il paraît que tu débutes en stéganogrphie ?
+
+En fait, dans chaque challenge on te fournira un fichier, et la première étape sera de determiner son type, car les étapes suivantes ne seront pas les mêmes en fonctions de si tu as récupé un jpeg, un pdf ou un mp3. La commande "file" te sera très utile.
+ +Une fois que tu auras récupéré cette info, tu devrais faire quelque recherches sur comment cacher des messages dans ce type de fichier particulier. Garde aussi en tête pour les futurs challenges que certains fichiers peuvent être valides pour plusieurs types, et que ça peut valoir le coup d'essayer de dézipper des fichiers qui ne ressemblent pas à des zip. Par ailleurs, la steganogrphie est traditionnellement l'art de cacher des informations dans les images, donc parfois tu auras juste besoin de regarder avec beaucoup d'attention pour trouver le flag.
+Voici un outil utile pour démarrer : https://github.com/exiftool/exiftool.
+Faire des recherches sur les métadonnées peut aussi être un bon point de départ.
+
+Bonne chance ! \ No newline at end of file diff --git a/fr/my_little_pwn.html b/fr/my_little_pwn.html new file mode 100644 index 0000000..a30c5b1 --- /dev/null +++ b/fr/my_little_pwn.html @@ -0,0 +1,13 @@ +Alors, il paraît que tu débutes en pwn ?
+
+En gros, dans presque tous les challenges, on te donnera un binaire compilé et un accès au serveur sur lequel tu pourras interagir avec le binaire. Parfois on te donnera aussi le code source (c'est le cas pour ce challenge).
+Ton objectif est généralement de lire le contenu d'un fichier "flag.txt" sur le serveur.
+Pour ça, tu auras besoin d'exploiter des vulnérabilités sur le binaire donné. Donc la première étape sera d'identifier ces vulnérabilités, puis de faire quelques recherches sur comment les exploiter.
+On te donne le binaire pour que tu puisses tester tout ça en local sur ta machine (qui doit tourner sur Linux pour la plupart des challenges, sinon le binaire ne s’exécutera pas).
+Pour ce challenge, je te conseille de chercher "buffer overflow" sur ton moteur de recherche préféré.
+
+Quand tu auras réussi à exploiter le binaire sur ta machine, connecte toi au serveur avec cette commande :
+nc challenges.42ctf.org 3002
+Bon courage !
+
+PS: n'oublie pas de télécharger les fichiers \ No newline at end of file diff --git a/fr/norminet_osint.html b/fr/norminet_osint.html new file mode 100644 index 0000000..dc818ad --- /dev/null +++ b/fr/norminet_osint.html @@ -0,0 +1,8 @@ +Oh no !
+J'ai refusé de donner le thon de mon sandwich a Norminet, alors pour se venger il nous a volé un flag !!
+Fais comme tu veux mais moi j'abandonne les recherches ce chat est beaucoup trop violent et il me fait peur !
+Je te laisse avec cette image, c'est la seule piste qu'on ait...
+
+### Tips
+
+Tu devras entourer le flag dans la balise "42CTF{}" avant de le valider. \ No newline at end of file diff --git a/fr/pas_les_bases.html b/fr/pas_les_bases.html new file mode 100644 index 0000000..0ba8571 --- /dev/null +++ b/fr/pas_les_bases.html @@ -0,0 +1 @@ +Il faut bien commencer quelque part, alors commençons par quelque chose de très basique. \ No newline at end of file diff --git a/fr/point_par_point.html b/fr/point_par_point.html new file mode 100644 index 0000000..0ffb206 --- /dev/null +++ b/fr/point_par_point.html @@ -0,0 +1 @@ +Un conseil pour réussir dans la stéganographie ? Etre pointilleux.

\ No newline at end of file diff --git a/fr/recycling.html b/fr/recycling.html new file mode 100644 index 0000000..442d619 --- /dev/null +++ b/fr/recycling.html @@ -0,0 +1,3 @@ +On nous a dit de jeter nos clés mais c'est quand même plus écolo de les réutiliser.

+ +Hint: Le flag est entre les balises 42CTF{} et les messages sont en anglais. \ No newline at end of file diff --git a/fr/silkway_v1.html b/fr/silkway_v1.html new file mode 100644 index 0000000..948f7b3 --- /dev/null +++ b/fr/silkway_v1.html @@ -0,0 +1,4 @@ +Les neo hackers du darknet profond ont développé un nouveau market, basé sur la blockchain, il serait ultra sécurisé. +Votre mission consiste à vider leur wallet bitcoin.

+ +Les outils de fuzzing tels que dirbuster, dirsearch, gobuster, wfuzz (liste non exhaustive) sont inutiles et interdits. \ No newline at end of file diff --git a/fr/the_answer.html b/fr/the_answer.html new file mode 100644 index 0000000..5cfc4e1 --- /dev/null +++ b/fr/the_answer.html @@ -0,0 +1,3 @@ +Alors, maintenant il est temps de mettre en pratique ce que vous avez appris dans le challenge d'intro.
+Rien de nouveau, n'oubliez pas de télécharger les fichiers et tout se passera bien.
+Quand vous serez prêts : nc challenges.42ctf.org 3001 \ No newline at end of file diff --git a/fr/we_need_a_pattern.html b/fr/we_need_a_pattern.html new file mode 100644 index 0000000..e3344a9 --- /dev/null +++ b/fr/we_need_a_pattern.html @@ -0,0 +1,6 @@ +Nous avons intercepté un texte chiffré avec un système de chiffrement inconnu.
+
+Nous pensons que le texte est écrit en anglais et qu'il contient des informations très importantes.
+
+ +Le flag est en majuscules, et entre les balises 42CTF{}. \ No newline at end of file