Hello everybody and welcome to this tutorial. Today, we will be importing
custom chains of proxies. Now I have done literally no prep work for this,
deliberately, because I want to see if I encounter any problems by doing this the
first time around on Kali Linux. And if I do, I want to resolve them here together
with you because if I encounter them chances are that you will encounter them
as well. So, automatically you will know how to solve them. But I
don't predict any special problems here, this should be fairly straightforward. So
let's just go and type in free sock5 proxies and see if we can find any for
ourselves. So Socks proxies - free socks5 and socks4 proxy lists. Let's see what this
website has to offer. Excellent! So we have a lot of these things here that we
can use anonymously, I suppose they all claim that they're anonymous,
but that's really questionable. So you
want to be using, generally you want to be using proxies in countries that have a
good reputation for not sharing your private browsing information, or
something like that. So, the countries that do have a good reputation with
that, well China doesn't share much with anybody else, Russia doesn't do that
either...there is the Netherlands as well, if they
have the Netherlands here that would be awesome because the Netherlands has
fantastic privacy policies in terms of information, in terms of personal and for
personal user information, and Germany is also not bad. So those are some of
the countries which you can use that are fantastic in terms of privacy. They will
not share your traffic with pretty much anyone, or so they say, or so they claim,
but, yeah. Who will you trust? That is completely up to you, but again it
doesn't really matter that much to you, primarily because most of the work that
we are doing here, or should I say all of the work that we will be doing
here, is white hat, and all of it is legal. So, you can use any of these to simulate
a real attack. And even if you can find, if you can reverse tracks and
find yourself, it's still okay as long as you are using some sort of a proxy to
give real-time circumstances, and encounter real time problems. Also, to
circumvent firewalls and so on. Because if you want to see Netflix, or something
like that, you will need a proxy in the United States. You most likely won't be able
to do it with the proxy, or you will be but you will need a really good one,
rather instead you will need a VPN. Anyway, without further ado, you have an
IP address here which we will need, you have a port number here, we won't need
this, we will need this, and we will need a version, so we'll need a version. I'm so
surprised, okay, there are multiple pages of the for this. So, actually, let's see if
there are any any proxies from the Netherlands. Nope, the Netherlands is
not even listed here, it doesn't exist. Okay, nevermind, I'm sure that it does
exist on some other websites. I have seen them and I have inclined to use
them primarily because they're good policies, but for our purpose today
it's truly irrelevant. So, let's just go ahead and select the first five from the
list. So I need to copy this, open up my terminal, and let's just make our screen
conveninient so we can do a ton load of copy pasting. There we go. Just do this,
and let's grab the Firefox browser, just expand it accordingly,
excellent! So I have everything that I need. I have the port number, version, and the
IP address. I need to expand the terminal a little bit to gain on size, excellent!
Clear the screen for any inconveniences, nano/etc/
proxychain.conf, make sure that dynamic is
is selected and everything else is commented out. Go scroll down to the
bottom, and let's go. Now we need to specify our proxychains. Go ahead and
start typing. Anything special we need to know here? No. Type host port,
user values, nope doesn't specify anything special. Let's go ahead and type
in, you don't need to use capital letters just so you know, so socks5. This first
one is it, yep, it is socks5, and paste the IP address. A bit of a longer IP
address, let's just go ahead and add tabs here to be on the
safe side, so that all is neatly done and sorted. So it's 33169,
press ENTER, so socks5, tab, what is the next one? The
next one is 9480. Paste it, tab, and the port
number is 1080. Let's take the next one, we just need to do
this a bit faster, so socks...oops, sorry, this one is actually socks4,
and the next one is actually socks5. So tab, as you can see it's a fairly simple
process, I mean there's nothing really special that you need to do here, just
create a list which you will end up using. I can assure
you that like more than half of these proxies do not work. Not because I can
see some information screen that you can't, but rather instead because I have had
experiences with such proxies, and they generally do not tend to work. But, enough
of them work for you to be able to anonymize yourself to a good extent. So
the next one is 1806, and zero. Make sure you get the ports
right, because if you get a wrong port your connections will be dropped by
default on that IP address, and you'll think that the proxy is malfunctioning,
or something like that, but it's not. It's just you typing in a
wrong port. So, again, we have socks5, an IP address here. What is the port
number? 1080 again. You will see that some port numbers have been standardized,
and they are just repeating, you don't need to do that much
thinking there. Press Enter, I just want to separate them from these, and let's go
ahead and control...oops, sorry.
No, I can just save it, it doesn't matter. Nope,
I don't want a different name...excellent!
I messed up the name. Okay, so, let's exit nano. Expand our beloved
terminal, the holy grail of power, type in pretty much the same thing as we typed
in the previous tutorials, proxychains firefox www.duckduckgo.com.
So just keep in mind you can type in any URL here, and as long as it's valid
it will open it. So let's just go ahead and see what happens. Press Enter...
nothing, literally nothing. What happened? It didn't even start
proxychains with it. Why not? Well, you need to close the browser first,
and we unfortunately had this list open that continuously keeps changing as well.
And that's a problem, because you cannot have Firefox open and then start it
again through proxychains. You need to close it completely, make sure that it
is completely closed, I can see nothing in my working menu down there, down at
the bottom of the screen, and let's try again. Same thing. See, now it's taking a
bit longer. As soon as you see that something flies
through with proxychains, using proxies that's really fast, you know that
something is wrong because there is no way it's gonna be fast. So what do we got
here? Timed out, timed out, again we have timeouts, and it's a dynamic chain so
it's trying to go through all of them, but it's skipping those that are not
functional. And I mean at the beginning stages, a long time ago, I
was like I'm gonna use 50 proxies and I'm gonna be completely anonymous. No, no,
I wasn't even able to load the basic of sites, or issue even the basic
of requests with that. You need to keep it low, in terms of proxies, depending on
their speed. Excellent! So, hopefully one of them is going to pass and one of them
is going to work. This is one way of looking at it and trying to figure it
out. Another way is just looking at the screen and see what's happening here. So,
I'm just waiting for at least one of them, yep, there we go. One of them said,
okay. But it needs to go and try all of the others out as well before it can
actually verify what is it that it's going to use in order to open this
site up. Hopefully, it's not gonna take too much time. So we have all
of these timeouts, and only one of them was okay. Which one was okay? DNS response
duckduckgo.com, there we go. It should be open now, no it is not. This was just a
DNS response. Is not exist? Hmm...have I mistyped this duckduckgo? No, I don't
believe I have. Okay, it's formulating a request again through a different series.
Come on, please succeed...excellent! This one didn't succeed...well,
now it has. DNS response is DuckDuckGo.com is 50.18.192.250. Have you opened? At
least tell me you have. No, you have not. Okay, we gotta wait a bit longer, and this is
the sad reality of using proxies. If I had used one or two
this would have been a lot simpler, but I just wanted to make a point here and
show you you're not gonna get anywhere if you're using a lot of free proxies.
And imagine scanning like a hundred hosts using proxychains like this, and
this would be the amount of time that it would take to even load a basic web site.
Imagine how long a scan would take. It would take forever. Okay, so finally,
finally it is requesting information on port 443. As you can see, all of the above
communication was attempting to get a response
from a DNS server. This is how much
information has been processed before we even started to
load duckduckgo.com. As you can see by the port names, it's 53, the 53 is
our DNS port. And if we go down, down, down below, you can see that finally I'm
looking for port 443 somewhere around here. I swear I saw it a moment ago...
1080 that's a proxy port. This is a proxy port as well.
53 again. DNS resolution port, yep, there we go, 443 has begun here. It's still
loading it. I wonder has it opened it? Yep, there we go. It is up and running, the
site is functional, but it has taken us a lot of time to open it using a lot of
free proxies. So stick to two or three at max and it should work, and stick with
the ones that have the best grades, reviews, and so on. Stick with the ones
that have the greatest uptime as well. That's one of the
routes that you can take. In any case, I bid you farewell,
and I hope to see you in the next tutorial.