raik’s ramblings

Sourcing.games: Game #2

2nd game, let’s go!

Level 1

  1. TIP: IN SOURCING, NOT ALL URLS ARE DEAD, THERE IS ALWAYS A WAY.
  2. Click the link “Get the password from the URL below”
  3. Click the button. The page tries to load, but nothing happens, why? Well, the url lacks a dot between www and the domain. Add a dot and you get the password.

Level 2

  1. In this task we need to find a man’s name from Microsoft’s homepage. From 1996. Too bad we can’t travel in time. Luckily we have the Internet Archive’s Wayback Machine. Plug in microsoft.com and search away. It’s that simple. I won’t spoon-feed you more than that.

Level 3 (or 4? This page was pretty funky)

  1. I assume there was some sort of a bug going on with this game, as I could just click to the next level without doing anything. The task given was also hard to understand for some reason, so I’m kind of clueless about what was the point of this one. Maybe inspect robots.txt on Linkedin.com?

Level 4

  1. Now this is a more interesting one. We’re given a password protected .docx-file, and to open it we need to find a GitHub user’s email, which will be the password.
  2. Let’s hop on to the GitHub page to see what we can find.
  3. I quickly glanced over the account, didn’t find the information we were asked for. So I did a little googling on how to figure out the email of a github user. Here’s the methodology:
    1. Go to a non-forked repo
    2. Find a commit made by the user
    3. Open the commit hash
    4. Append “.patch” to the url of the commit hash page
    5. Once the patch view is open, you’ll see the email of the person who made the commit on the 2nd line
  4. Now we just need to grab the part before @ sign in the email, use it as a password for the file grab the password within. That was fun!

Sadly, this is where it ends for us currently. The password found on the file doesn’t do anything when input on the site. Since there was some weirdness happening before, I can only suspect that there is something wrong with the site. Different browsers or clearing the cache didn’t work. What a shame! I will update this post later if the problems are fixed.