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

Поделиться
HTML-код
  • Опубликовано: 24 ноя 2024

Комментарии • 16

  • @larsla
    @larsla 2 года назад +51

    "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

    • @__hetz
      @__hetz 2 года назад +3

      First official message transmitted from the Supreme Court chambers, then located inside the Capitol. I took a handful of footnotes with pico this year because of interesting cipher text or flags. Very fun!

  • @greyether777
    @greyether777 2 года назад +3

    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!!

  • @JohnSmith-eq5bw
    @JohnSmith-eq5bw 2 года назад +1

    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.

  • @scizophreniac
    @scizophreniac 2 года назад +5

    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

    • @charliegreen4128
      @charliegreen4128 2 года назад

      Tried the decoders... Didn't get great results. Just did it manual. Was honestly a lot more rewarding.
      It's hard to know sometimes what the best solution is in terms of learning/experience. A lot of the writeups wind up just jumping straight to the easy solve. Which a lot of the time frustrates me because it doesn't explain anything. Idk of they know it, but if I'm there, I probably don't.
      At the same time, working out that there's a script in this challenge somewhere is great and saves a lot of work.

  • @petehinch3871
    @petehinch3871 2 года назад +3

    Can you put this in a playlist please John. Thanks for the videos as always

  • @poprivest4715
    @poprivest4715 2 года назад +1

    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 :)

  • @hutch0561
    @hutch0561 2 года назад +8

    I just used morse2ascii tool in the Kali terminal and ran the file through that and it worked great

  • @sb77de
    @sb77de 2 года назад +1

    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
    @Lacsap3366 2 года назад

    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.

  • @jacobsilva421
    @jacobsilva421 2 года назад +1

    Audacity and cyber chef for this one

  • @marounahel8205
    @marounahel8205 Год назад

    king thank youu

  • @nytobarros7248
    @nytobarros7248 Год назад

    Made a python script for decrypt those...on my github....nytorj

  • @prakasakatheilluminator6904
    @prakasakatheilluminator6904 2 года назад +1

    those characters doesn't make any sense... i don't know what creator was thinking while creating that challenge...