S s h stands for a secure shell and works on Port 22.
It helps administrators make operations over an encrypted channel.
Although SS age might come in handy when you want to access remote systems.
Sometimes, but not so often, but it's good to be aware of it.
S.H. itself can have some configuration vulnerabilities.
So let me just quickly show you an example of a poorly configured as S.H. server.
So first, let's search for S.H. Auxiliaries.
There are too many module's.
And I'll follow the same sequence that I did in the previous videos, and I'll try to discover the version
users.
So I will pick S.H. version as my first module.
So the options.
Now, because I said the are hosts variable as global, the value is automatically assigned.
And there's nothing change here, so let's run the module.
And here's a result, so it contains more details on the SSA services on both machines.
You should also make a note of that.
Now, I don't want to look for vulnerabilities for these versions, but you can if you want to, and
test him in the lab environments if you find any.
So, OK, then I'm going to use S.H. log in as my next module.
Swaptions.
And I will allow the user name as password.
And except blank passwords.
Now, I won't create a dictionary file again.
So I'm going to use the file that I created for FTP.
And I don't think we need anything more, so let's run the module.
Now, here I get a username, password Perre, vagrant, vagrant, remember that also.
And then metastable point automatically opens its session for us on board 22.
So now we can interact with that session.
So now let's enumerate the next service.