Morse Code for CTFs (PicoCTF 2022 #16 'morse-code')

13,532
0
Published 2022-04-26
Help the channel grow with a Like, Comment, & Subscribe!
❤️ Support ➡ j-h.io/patreonj-h.io/paypalj-h.io/buymeacoffee
Check out the affiliates below for more free or discounted learning!
🖥️ Zero-Point Security ➡ Certified Red Team Operator j-h.io/crto
💻Zero-Point Security ➡ C2 Development with C# j-h.io/c2dev
👨🏻‍💻7aSecurity ➡ Hacking Courses & Pentesting j-h.io/7asecurity
📗Humble Bundle ➡ j-h.io/humblebundle
🐶Snyk ➡ j-h.io/snyk

🌎Follow me! ➡ j-h.io/discordj-h.io/twitterj-h.io/linkedinj-h.io/instagramj-h.io/tiktok

📧Contact me! (I may be very slow to respond or completely unable to)
🤝Sponsorship Inquiries ➡ j-h.io/sponsorship
🚩 CTF Hosting Requests ➡ j-h.io/ctf
🎤 Speaking Requests ➡ j-h.io/speaking
💥 Malware Submission ➡ j-h.io/malware
❓ Everything Else ➡ j-h.io/etc

All Comments (14)
  • @larsla
    "What hath God wrought", the official first Morse code message transmitted in the US on May 24, 1844, to officially open the Baltimore–Washington telegraph line -- Wikipedia
  • @greyether777
    No time wasted! I like your approach to trying several different avenues or "nerd out" as you say, lol because it helps us noobs get a realistic view of CTFs. That we're not always going to just sit down get it the first try. Thanks so much John!!
  • This is an interesting example of the value of a diverse knowledge base. Technical knowledge is essential, but knowledge of history and linguistics are extremely helpful for identifying the flag. It seemed like John, a HIGHLY educated security pro, was thrown by the use of an archaic past participle in that historical quote.
  • @petehinch3871
    Can you put this in a playlist please John. Thanks for the videos as always
  • @poprivest4715
    I'd like too point out that mplayer did recognize this as a 1 channel pulse, 2 bytes per sample. I didn't get into it but there's probably a way to do this with a hex editor or something similar, just analyzing the bytes figuring out the dots, dashes and pauses. Just a thought :)
  • @scizophreniac
    i did this one a bit more "manual" and opened the file in an audio editor and looking at the "spikes" small spike == . long spike == _ long silence was a space, and then put the result into a normal text morse decoder, didn't think of finding a audio morse decoder. kinda glad i didnt, felt like more of a proper challenge this way :P
  • @sb77de
    My audio analysis matched Audacity matched some web service I ran this through but it just wouldn't take my flag... should've kept guessing x)
  • @Lacsap3366
    haha I actually went ahead and translated the sound by looking at the graphs in Audacity to dots and lines using my eyes. Threw that into cyberchef "from morse code" and I got the right flag.
  • @hutch0561
    I just used morse2ascii tool in the Kali terminal and ran the file through that and it worked great
  • Made a python script for decrypt those...on my github....nytorj
  • those characters doesn't make any sense... i don't know what creator was thinking while creating that challenge...