So that's Firefox covered.
Let's go ahead and take a look at Chrome now again for HTP.
As we mentioned, everything works as expected.
It's a very simple scenario, four steps.
You still want to use the same configuration as Firefox.
So we're going to use the custom Kali, which comes with the latest better cap and a custom steps hijack
couplet.
Everything will work as expected in this case.
The only thing is you need to make sure that you input to the target website in the STC hijack couplet.
So similar to what we did with these websites, you're actually going to have to include all of the
steps websites that you want to target and you want to downgrade to HTP in your steps hijack couplet.
So it's a bit of a limitation, but that's the only way we can do it.
With the latest version of Chrome, for example, we have Netflix.
So as we know, Netflix worked perfectly fine in here.
So let me just go quickly on Firefox.
Netflix dot com.
And as you can see, it's loaded in perfectly fine.
Now, if I load that now on Chrome with the exact same configuration of Buttercup as you know, it's
already running.
It's going to load over https and not FTP.
The only way around this is to actually go back to my Carli machine, open up my file manager, and
open up the SDS hijack couplet so you can do a control l to do that.
Or you could press in here and press a forward slash and it's stored in you as our.
Local share.
Better cup upsets.
Stars hijack.
And the couplet that we want to modify is it's hijacked cup.
So it's this couplet right here.
We're going to right click it and open it with another application you all and open it with my leaf
pad with the text editor.
So I showed you how to do all of this and the stars bypass lecture.
That's why I'm doing it fast.
Please revise if you don't remember.
And what you need to do is simply in here.
Input the steps websites that you want to downgrade to HTTP.
So in this example, we want to downgrade Netflix dot com.
So we're going to input it in here and I'm going to select it again and I'm actually going to put it
in the next RAW and the Replacements as well.
And finally, we're going to put it in the DNS spoof.
We're going to save, quit, and we're going to go up and run.
Better cop again.
So I'm going to exit.
Clear the screen.
Run.
Better cop with this proof couplet.
And then run the SDS.
Hijack couplet.
And let's go ahead and test this with Chrome.
So before testing, think it's always a good idea to remove all browsing data.
So control, shift, delete, make sure all time is selected and make sure you take all of the boxes.
We're going to clear.
And let's go ahead and go to Netflix dot com.
Hit enter.
And perfect.
As you can see, Netflix is loading over normal http now.
So again, if you're inputting any username and passwords in here, you'll be able to capture them and
you'll be able to modify this website and the requests on the fly because everything is sent over HTTP
which does not use any encryption.
And we will cover that later on in the course.
So the main idea is all you have to do is simply add the websites that you want to downgrade to FTP
in your sites, hijack, couple it.
So that's his two tips for Chrome, Don.
Let's go ahead and take a look at preloaded websites on Chrome.
This will work exactly the same as Firefox.
So you're going to need to use the custom car with the better car with the custom.
Hey, just yes.
Hijack couplet and similar to what we did with Firefox.
The targets will have to be in the lists, hijack couplets.
So we're not doing anything out of the ordinary.
The only thing is secure.
DNS needs to be disabled.
So secure DNS is a setting that Chrome has and if it is enabled, the web browser is going to use encryption
when making DNS requests and therefore it'll render our attack right here with the custom hosts hijack
couplet useless.
Now the good thing is secure DNS is not always enabled by default.
It depends on the country of the target.
For example, in Ireland, if you download the latest Chrome Web browser, it's actually going to come
with secure DNS enabled and therefore the attack is not going to work unless it is disabled.
So if your target is in a country where secured DNS is not enabled by default, chances are they don't
even know about this option and it's probably going to be disabled and therefore the attack will work.
So let me show you where this setting is.
In my chrome if we go to settings.
And we can use the search icon in here to search for that setting.
And we want to search for secure DNS.
And as you can see, is telling us it's in the security settings.
And if we scroll down.
You will notice that you secure DNS is enabled.
So if I just turned this off.
And close this one, though, and let's go ahead and test the attack exactly the same way that we tested
it before.
So we're going to go to a local Google Domain, for example, Google Dot IEEE.
As you can see, it's loading as normal FTP, not https.
Therefore, the SDS hijack couplet is going to be able to modify this page, play with it, and change
the links to those corn.
And let's look for Twitter.
And again, if we go over here over the link, you'll notice at the bottom it's twitter.com now, but
literally within a second it's going to go back to being Twitter dot corn.
Let's open it in a new tab.
And perfect.
As you can see, Twitter is loading over normal FTP.
And again now if the user logs in, we will capture everything or because the website is loading over
normal FTP, we're going to be able to inject anything that we want and modify the website and inject
evil code in it.
And I'm going to show you how to do all of that later on.