 Hello, what is going on everybody welcome back in the YouTube video and in this video and the next couple or few I want to be going through some some video walk-throughs and guides for the Linux offset club and it's a online war game that you can find at Linux off sec club and You can see here. It gives us some credentials a username and a host name Password first log into in the directions are SSH into this user with that password use the home directory of that user to find The next password etc and user 15 is the last user. So I am going to go through video guides for every single one of these levels all of these users and I'll release them kind of steadily. It's just kind of like three at a time just three of those hopefully stretched out to like five videos and I know here. Okay. This is created and maintained by the offensive security club at Dakota State University So shout out to you guys. You're awesome. Thanks for creating this thing I Don't know if I already did have this folder created. Okay. It looks like I did whatever Let's jump in let's make a directory so we can work in this and I'm gonna go ahead and copy this password Put it in a user one dot text file So we can keep track of them and then let's just start. Let's SSH into this account user one at Linux dot offset club and I'll paste with control shift V that password and I Forgot the spaces in there in the clipboard. Okay, cool. So here we are we are I Totally jumped over this message of the day, but it's not important If I were LS, there's nothing in this directory, but I am in the home directory So LS in that there's nothing in this directory, but only Not including hidden files if I LS tack a to denote all these hidden files We get something else here. In fact, we get a hidden directory called dot here That looks kind of different than what we're used to normally We're used to seeing a bash history bash logout bash RC profile in SSH folder, but we don't normally see a dot here So let's check out that I can tell it's a directory because it is blue for LS colors You could probably run LS tack L if you need to see that more strictly, but I'm sure you're used to this Stuff LS there's our pass file. Okay, cool. So this is the password for user two Let's just note that in a another file cool Close that alone and Now we can SSH into user two Let's copy paste that password suite. We're logged in and there's this file Called dollar sign exclamation point backslash password and and percent and yeah, okay, that's that's totally the file But can I actually cat that file? No, I can't it makes my shell go crazy and weird. Okay, whatever not to fret we can use a wildcard here, right? We can Just cat star And we get the file. Okay, so that wildcard that star that asterisk is just Treating every character and interpreting it. Okay as encompassing as many characters as it can So it's reevaluating to this this file name and is able to actually display it to the screen a okay So, okay, there's our there's our password for the next one. Let's jot that down in user three dot text cool Break out of this guy and SSH to user three Paste that password in and we're moving. Okay Passwords just in this directory. Oh, okay Different thing here, right? This isn't a regular password. Excuse me This is an SSH private key that we can use to actually connect to I'm assuming the next user user four, right? You can Kind of identify these by this by default mii base 64 string that kind of knows. Okay This is the credentials that you typically see in an rsa private key and when you're making SSH connections Sorry SSH connections You can have an rsa private key act as your password act as your credential to actually log in and authenticate to so let's just copy this and I'll break out of here. Put this in user four dot text I'll copy this in and Remove all the new lines. Whoops. Okay, good There is no new line there whatever So now rather than SSHing and expecting a password we can use tack I Specify that private key file and it's called user four dot text Okay, it's given us a warning. Hey is an unprotected private key file the permissions zero six six four for that file are too open You don't want your private key to be accessible by others You'll see this pretty much all the time when you want to try an SSH with a private key It needs to be not accessible by others only you so let's control C to break out of that LS tack L. Oh, sorry. I'm not in my user My my litics offset group my bad. Oh, I don't have user. I don't have user one in here Okay, cool sweet. All right LS tack L and now user four you can see the permissions on here are read write by me Read write by group and read by everyone. So let's change these up with CH mod Modify the permissions and I'm going to use six zero zero as an I can read and write group cannot do anything and everyone cannot do anything on user four dot text Now LS hack L. Okay, cool. I can read and write. No one else can do anything else That should be the appropriate permissions to use that SSH command Let's try it It's a check I user four blah blah blah Cool, and we're logged in. All right. Awesome Let's tackle Levels and users four through six in a next video, but I don't want to make this one too long Thank you guys for watching. Hope you enjoyed these and hope this will be a quick and easy good series for you guys to Kind of munch on. All right. See you later