Hi, we are in the band at level 27 and we want to go into the 28 and here we have these get tips over
here.
So this level is about get.
And if you are a software developer, I assume you know about the get get is a version control system.
We use it to version control of our projects version control our codes we use in.
We use it to publish our codes to the GitHub and so much more.
If you are a developer, you should know about this.
And if you're a cybersecurity specialist, you should know about this as well.
So this level is about get if you get in the server, as you can see, we can use the get we can use
to get commands.
We're going to have to, you know, a little bit about this get stuff in order to solve this problem,
I believe, because it says that there is a git repository in the in one of the folders or one of the
files over here.
And we have the password in the git repository.
So Git Repository is actually a project.
OK, so you write a code, you create a project and you save it under the under your git repository
show that you can reach that git repository later on to do some operations.
For example, if you can, if you want to, you can create a save point, which is a comment in the
get OK.
In that same point you actually are at a point where you are satisfied with your project.
So if anything happens, like if you break something, you can't fall back to that point.
If you want, you can check out to that comment later on.
So let me show you what I mean.
Go to the GitHub dot com, slash my name until someone sillu.
So it's spelled like this.
OK, just look at my browser.
You can go to any repository you want, but you can just go to mine and you can see I have a lot of
repositories since I'm a software developer as well.
I can go into my python cars over here and I can see all the available files and folders for me, all
the codes that I have been working on, all the checkpoints, all the comments that I have done over
here.
So let me show you what I mean.
So in this case, we can say we've code and over here I have a lot of Python notebooks.
So let me go into one of them, like in one by one py file over here, we can see the code and stuff.
As you can see, we used the git in order to create a repository and over that repository I can do whatever
I want.
So let me come over here and write Git Clone and paste that SNH Eurorail over here and it says that
permission denied.
I'm going to tell you what cloning means.
Don't worry, I'm going to create a temporary folder over here.
OK, so I'm going to call this temp till twenty seven.
Since we are in twenty seven, I'm going to seed into that and I'm going to run the same code, get
clone and I'm going to say yes.
So cloning means and it asks for a password.
So I believe we have to give the password for the level twenty seven over here.
I'm going to just say Paiste collection.
Yeah.
Here you go.
So clothing means that copying that repo to my own server, to my own computer.
Now wi fi around Al-Saleh.
Here you go.
We have the repository and we only have a readme file.
Now if I kept that file.
Here you go.
We have the password.
So this is relatively easy.
We didn't have anything to do.
We we just closed it.
OK, but we have learned about cloning.
Right.
So cloning means downloading that repo to your own project, to your own computer, to your own server.
So I'm going to narrow this password over here and just pasted over there.
So this is level twenty six.
Oh, no, twenty eight.
And this is level not level.
So I'm going to save this one and I'm going to come back here to exit out of that one and to log to
twenty eight or dare.
So as you can see it was fairly easy.
We cloned it, we had, we had just seen the read me files and we found the password.
Let's see what else we have in twenty eight.
Let's see if it's related to get again.
Let's.
Let's come over here.
Yep, it's related to get again.
So again, there is a great repository at some server and we're going to clone the repository to see
what we can do with it.
I'm going to just make another directory over here, OK?
I'm going to call this until 28.
I'm going to KDA into that and I'm going to clone the thing again.
And in order to clone, I will just from git clone one more time and paste the selection and it will
download the project for me and for the password.
Of course, I'm going to get the password txi and just copy and paste this thing.
So as you can see, keeping logs of our passwords is very efficient and very necessary at this point.
So if you're on, the less we can see the ripple folder over here.
If we were on the SLA one more time, we have the README and here you go.
We see the username and we see the password.
But password is actually kind of encrypted.
So commands you may need to solve this level is get so we have to dig deep, dive into the commands
over here.
So what did I say before we can use the git in order to create checkpoints.
OK, and there are a couple of things.
If you come across in a situation like that that you should do, you have to check some comments.
You have to check, get branch, OK, get branch.
Ah, so it shows you the different branches that you are inside or different branches available.
You can't run get branch to see the current branch that you're in.
We are in the master branch.
I'm going to tell you what a branch is later on.
Just so you know, we are in the master branch right now.
We don't need to do anything.
You can search for GTECH.
We don't have any tags into the repo.
You can search for get log and you can see all the comments that have been done for this project.
So what was the what was committing?
What were the comments?
So these are check points.
Then when a developer write some code, then he is satisfied.
When she is satisfied with the current level, they can just say commit this changes to my repository
so that I can come back here or go forward in time in order to just deal with my project.
And in this case, as you can see, it says fix info leak.
So this is a complete message.
When you commit something, it asks you for a message.
OK, so developer has written fix info leak, so most probably at some point developer fix the info
leak.
And if we come back in time, like if we go to that comment, that particular comment, we may reverse
the thing that she has done so well.
We can say we can just say check out and we can just copy and paste that hash.
And here we go.
Now I'm going to run Ellerslie.
So nothing has been changed.
Apparently, we only have read me one more time.
OK, but if I kept this, then I will see the password over here.
So what happened?
The developer fix that problem.
OK, they erased the password.
They just put X, X, X, X and then committed and we undo that comment.
OK, so I'm going to save this to my password texta and I'm going to exit out of this one and I'm going
to login into the band, the twenty nine.
So here you go.
So let's see if this is the right one and let's paste this and hit enter.
So here you go.
We are inside of the banded twenty nine and let's see if this is about get as well.
If this is about to get I'm going to continue solving it.
Yeah.
Here we go again.
This is the same thing.
I'm just going to clone that one and see what this is about.
I'm going to make directory under Tempy.
I'm going to call this until twenty nine and I'm into that and then I'm going to get clone and just
paste is over here and we're going to need the password one more time.
So let me get the password and let me get the password from here and come over here and just paste selection.
Here you go.
Now we are inside of the band the twenty nine and we can see the repo.
Let me Al-Saleh.
And here you go again.
We don't have anything if we can.
Read me.
It says that no password's in production.
So, again, there are some standard things that we should do.
We can check the jetlag, we can check the tag.
And here we have the fix username and initial comment of read me.
OK, so we can try to go back to that comment and see if it changes and think, OK, or we can try to
just see if we have any tags like e-TAG or Branch where inside of M. But as you can see, we have a
lot of branches over here.
So branches are different ways that you can go in your project so you can create a test branch, for
example, and just go back whenever you want so that you won't break anything.
So I'm going to just say check out that.
So if I write Get Branch right now, I mean that branch rather than Master Branch.
So that means means development.
Now, since we actually changed the branch, we can check the git log one more time and we can check
the read me one more time because it has been completely changed for us.
For example, in jetlag, we see a lot of logs over here, as you can see.
Right.
So let me get with me and here you go.
We already see it.
If we hadn't seen this, we would try to go back into the other comments again with the git check out
command.
But right now we can see the password.
So I'm going to copy this one and I'm going to just narrow into this and I'm going to save the level
30 over here.
So far, so good.
I'm actually I'm trying to do this a little bit fast because I believe you.
If you have come to this point now, you're a little bit fluent about this.
Now nothing gets into, OK, I'm not wasting any time to explain the things that we have done so far.
So far, so good.
Let me go into the band of thirty and let's see if this is about get as well.
Let me come over here.
Yep.
This time is this is about get as well and it doesn't give us any specifications.
We're going to have to do the same thing one more time.
Let me go into the temp until thirty and I'm going to go into temp until thirty and I'm going to get
on this project and let me pass this over here and say yes and lets me get the password one more time.
So let me just copy this and come back and pass it over there and here you go.
We have managed to clone it.
So if I were on there, let's play.
We can see the repo.
Let me run this play and let me just get the read me files.
And it's just an empty file and it loves us.
So very good.
So let me just go to get Branch and we only have the master branch over here.
Let me run.
Good luck.
And there is only one Gitlow over here.
One comment and then you tag.
We have the secret thingy going on.
I believe we have to go for that.
It's pretty obvious, right?
So you can't use tags and if you say get shot secret, it will show the secret for us.
So it may be the password for the next level.
Right.
So come over here and just pass it over there and let's go to level thirty one.
So it was pretty easy as well.
I believe these are all designed for us to learn about Git.
But if you're a developer like me, you have done this like a thousand times.
So you know how to work with Git and you can just proceed over here a little bit faster.
So let me come over here and say, enter, let me come over there and let me go back to here to go into
level thirty one.
And this is about get as well.
Let's see.
Yep.
So I'm going to get on that one this time.
So I'm going to copy this.
I'm going to just make a directory in the TMP folder say until thirty one I'm going to QD into that
folder on top until thirty one and I'm just going to get on that one and we're going to need the password.
Let's go back for password, let's get the password and let's get the password from here and say copy
selection and come over here and paste the selection and let's see if we have the repo, if we go to
repo and if we run out of Salay, let's see, we have the get Egner.
So let me get the read me.
First of all, it says that this time your task is to push a file to the remote repository.
OK, we can do that.
We get pushed by the way, details filename Keidar text content.
May I come in branch master.
So it asks us to create a file called Ketut Texte and inside of KeyData acce.
We should have.
May I come in ok with the question marks and everything like that and we will push that file but we
have to check that get ignored first because getting ignored means that ignore some files.
If we have the KeyData in there, even though we create this and we push this, it won't get allowed
in the git repository because git ignore is created for that stuff.
OK, ignores some of the files in the git repository.
It's created to keep it secure like you want to keep keep the server keys for example, safe.
You don't want to push them to your get reports or other people cannot see them anyway.
I'm just going to get this and yeah this is actually a little bit different than what I expect to see.
It ignores every text file, so it is pretty obvious what we should do.
We can either change to get ignore content or we can just remove it right before we create our file.
So I'm going to just R.M. to get ignore file and I'm going to run an SLA.
As you can see, we got rid of that, getting our files so we won't be ignoring the text files.
So it's pretty trivial to create the KeyData with that content.
You can't use the Echo command, you can use the Vim.
We cannot use the Nano for some reason in this case in the server.
So I'm going to say Echo and I'm going to just write, may I come in?
But just beware the questionmark and all the other things, OK?
May I come in?
I'm going to take this output and put it into something called KeyData Sixty.
Now if I run Al-Saleh I will say I will see the KeyData ACCE and if I kept the KeyData I will see.
May I come in.
So we're going to push that to the remote to.
Story in order to do that, first of all, we need to commit our changes.
So right now we're going to do our own comit, so we're going to save our changes, OK?
And let me see if we have anything else.
As you can see, it says, may I come in?
And this is exactly what we have written.
So I believe it's we are fine.
So we are in the master branch.
We have the file that we need or we need to just push it.
So I'm going to say get Ed KeyData.
This will add the file to our repository.
I'm going to commit the thing.
And we need to give a complete message by saying that I am no comment, OK?
Of course you need to be more specific in real life cases.
So over here, it says that there is a new commitment file change, one insertion.
So I'm just going to push this.
I'm going to say get push and say yes.
And it asks for the password one more time.
Let me copy the password from here, OK?
And I'm going to come back and just pasted over there and I will hit enter and here you go.
Now it got pushed and well done.
Here is the password for the next level.
So this is the password for the level thirty two.
Great.
So let me just copy this one over here, OK.
And let me come over here and just say NENO and save the password over there.
So I'm going to paste this thing in and I'm going to save it this level.
Thirty two.
So great.
Let me come back over here and exit out of this one and I'm just going to try and connect to Bendit
twenty thirty two in order to test the password that we have found so great.
I believe this will be one of the last sections if it's not the last section itself.
And let me try and see.
Yep.
Here you go.
Level thirty two to level 33.
After all this stuff, it's time for another escape.
Good luck.
So great.
Again, we are off to a new challenge.
We're going to see what it means in the next level.
And as you can see, the uppercase show.
So it's interesting.
Let's do that within the next lecture.