Level: 0→1
Level: 1→2
Level: 2→3
Level: 3→4
Level: 4→5
Level: 5→6
Level: 6→7
Level: 7→8
Level: 8→9
Level: 9→10
Level: 10→11
Level: 11→12
Level: 12→13
Level: 13→14
Level: 14→15
Level: 15→16
Level: 16→17
Level: 17→18
Level: 18→19
Level: 19→20
Level: 20→21
Level: 21→22
Level: 22→23
Level: 23→24
Level: 24→25
Level: 25→26
Level: 26→27
Level: 27→28
Level: 28→29
Level: 29→30
Level: 30→31
Level: 31→32
Level: 32→33
Level: 33→34

~ Level 30→31 ~

Level Description

There is a git repository at ssh://bandit30-git@localhost/home/bandit30-git/repo. The password for the user bandit30-git is the same as for the user bandit30.

Clone the repository and find the password for the next level.

The command suite of git is needed for this level.

Research Before Solving

Research will be completed as we delve deeper into the level.

Solution Walkthrough

We will begin this level the same way as the last two. By first creating a directory, /tmp/user and then moving into it. We must then clone the provided repository git clone ssh://bandit30-git@localhost/home/bandit30-git/repo. Confirm the connection and enter the password.

Use ls and then cd repo. After using another ls, we will read the file called README.md.

Using git log we find that only one commit is available. The aforementioned commit is just of the empty file shown above.

Issuing an ls -a will allow us to see a hidden directory by the name of .git. Let's move into this directory and have a look around. While perusing through this directory we eventually find a file named packed-refs. The contents of this file are shown below:

The third line from the top is the repository that we cloned. The next item down points to something called refs/tag/secret. Secret sounds like something we might be interested in!

Using a search engine, we find that refs stands for references. These are files that contain the hash of a committed object. The hashes in the above picture are the long strings of characters. This packed-refs file simply stores all commits of files in one easily accesible place. Research into tags tells us that a tag is used to mark a specific, important point during a commit files history. We can use git tag to list all tag objects within the repository.

using command of git tag to show all tags

Going through the man pages of git we then find we can use git show to look at the contents of specific objects. In this case, we use git show secret to see its contents:

We've found the password to level 31! Delete the directory that we created using rm -rf /tmp/user before tackling the next level.

Password: 47e603bb428404d265f59c42920d81e5

Previous Level

Next Level