Hey everyone !

With so many people stuck at 200 points on the board, I’m wondering if the chapter 2 isn’t too “abstract” ?

The Cyb3r Hunt is meant to be challenging, but it shouldn’t discourage players because they can’t figure out what to do.

For those that went past it, did you find the solution sketchy ? Did it all make sense, or you went past it without really understanding what all these files were for ?

For those stuck, where are you stuck at (please use a spoiler tag) ?

I’m considering removing some files I consider “optional”, and changing the hint to make it less like a guessing game as to what to do.

Any opinions on this ?

  • z3braOPM
    2•8 months ago

    Thanks for this very detailed answer !

    chapter 0x02

    You did right with curl. Though there are other gopher clients that could have worked this way (but not all of them support torsocks).

    The Ygg part is what I want to make more clear, because when you’re at the gopher hole, you shouldn’t really care about the nmap/passwd/wtmp file. Your only goal should be to setup Ygg and proceed with the info from the wiki. And that’s definitely not clear enough from the feedbacks I got from this chapter.

    Now regarding your current problem on chapt.3:

    chapter 0x03

    “chisel” is only there because I couldn’t find a better rhyme haha. Now to get you onto the correct direction: there are 2 socks5 proxies. One that you can use right away to only let you fetch the puzzle, and one that you’ll use later on to get full access to the mine. Perhaps I should look into making the hint more explicit at this stage too. I’ll look into it ;)

    Thanks for your feedback, I’m glad you’re enjoying it and hope you’ll get through it, because the funniest part remains !

    • sivanataraja
      1•8 months ago

      Thanks a lot for your help!

      spoiler

      My next move was to try and install https://github.com/jpillora/chisel to fetch the content via git protocol through the proxy because I cannot force git(1) to use the SOCKS5 proxy (no option seems to work: it’s only with https or http). So, maybe chisel was just there for the rhyme. Still trying…

      • z3braOPM
        2•8 months ago

        Oh wow I had no idea this existed, but yeah at first glance, this looks like a dead-end. That’s definitely not how you’re supposed to do it (and it doesn’t look like it could work anyway).

        ::: spoiler You were on the right track at first, except it’s not http. Look for other proxy settings in git-config(1) :::