So there are minor differences between Windows and Linux interpretive sessions.
This is why I'd like to show you the interpreter session in both machines.
In our last lecture, we had an interpreter session on meds, bootable Linux machine.
Let's continue to see the basic interpreter commands on that session.
So a good habit to get into is looking at this disinfo, which is the first command that I run when
I interact with an interpreter session, just so I can see which system I am in.
Never hurts to double check.
OK, I'm on meds.
Help is the second command I'd like to show, and not surprisingly, it shows the available commands
in this meditative session.
Commands are grouped and we'll talk about it more in the following lectures about the command names
are at the left hand side in the descriptions of commands are on the right hand side.
And here's another command group anyway.
So first of all, let's see how we can manage interpreters sessions.
If you're in a mature session, you can go back to MSF console with the background command and now we're
on MSF show.
Sessions L is to list the active sessions now the sessions may or may not be interpretor sessions,
but you'll see the session type in the third column of the sessions list.
In fact, the Sessions command with no parameter lists the sessions as well, so you don't need to use
the URL parameter.
The first column of the list shows the ID numbers of the sessions information column shows the user
and the system connected and the connection column shows the attacker and the victim systems IP addresses
and the connected ports.
The Sessions command with the eye parameter to interact with any of these sessions simply give the idea
of the session you want to interact with.
And we're in the Mediterranean recession of the Mideast voidable Linux again.
Now to see our current position in the target system.
We'll use the P WD command.
OK, if you're familiar with the Linux system, you already know that the command is a standard Linux
command to print working directly.
Well, you're wrong.
Here, it's a maternity command and it runs under the other operating system sessions as well, which
I'll show you in a couple of minutes.
The interpreter filesystem commands are mostly similar to the Linux file system command.
We're on the route folder, we can use the Alaska man to see the files in this folder.
The CD command to change or to move to another folder, for example, Etsy.
And now we are in ETSI folk.
So we can use the CD command to go back to the root folder again.
The next command is yet Eweida.
It's used to show which user you are on that system, we are the route user, which is very good for
us, but not for the victim.
Get pide is to see the ID number of the process that we are injected into.
But it seems it's not available on Linux systems.
OK, I'll show it on a Windows system soon.
Stay tuned.
The command is to see the running processes on that system.
So harsh dump is a very useful command for ethical hackers, as you might guess, it lists the hashes
of the user of this system.
But remember, you can access the hash files if you have the route or the admin privileges.
Otherwise, interpreter cannot gather the hashes.
But don't worry, there are a few tricks up our sleeves to escalate the privilege.
Well, now it seems the interpreter does not have the hash don't command for Linux systems, but again,
no worries because we can use a post module to gather hashes.
We'll see that in detail in the post exploitation lecture.
So just to show you that we have alternatives, let's run this post exploitation module.
Run post.
No wind, no, not Windows, it's a Linux system.
Regathered, hash, dump and hit Aitor, remember, Métis Boyd, framework and interpreter have code
completion.
So you can just use the tab key to complete the words, and here are the usernames and the password
hashes.
Now, I don't know if I need to stress to you that this is very important data, so we'll use these
hashes for some of our purposes a little bit later.
But first, let me show you that idle time is another useful interpretive command, which displays the
number of seconds that the user at the remote machine has been idle.
If you'd like to log out the user or restart the.