Way To Hackintosh

SSH Tunneling Explained

Admin Jixxi 0 5 things a Beginner Hacker should know, BEGINNERS, EXPLANATION, EXPLANATION ABOUT, SSH Tunneling Explained

<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZ_N7NUQvAEB8vbEenDFN0aHDiOvQOOdIr0Xd6EA-bOSZuE4UPSvCJzkIw4_RzzMMzHRnDo-8qRhPHUz6v6sT3W_xY-Z9Q7VRVgzIyZ8dcq2Aqrc_WcRnRgwlTJmb29wsivZTbuIOYow3m/s1600/localportforwarding.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="152" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZ_N7NUQvAEB8vbEenDFN0aHDiOvQOOdIr0Xd6EA-bOSZuE4UPSvCJzkIw4_RzzMMzHRnDo-8qRhPHUz6v6sT3W_xY-Z9Q7VRVgzIyZ8dcq2Aqrc_WcRnRgwlTJmb29wsivZTbuIOYow3m/s320/localportforwarding.jpg" width="320" /></a></div>
Recently I wanted to set up a remote desktop sharing session from 
home pc to my laptop. While going through the set up guide I came across
 ssh tunneling. Even though there are many articles on the subject still
 it took me a considerable amount of googling, some experimenting and 
couple of Wireshark sessions to grasp what’s going under the hood. Most 
of the guides were incomplete in terms of explaining the concept which 
left me desiring for a good article on the subject with some explanatory
 illustrations. So I decided to write it my self. So here goes…<br />

<h3 style="text-align: justify;">
Introduction</h3>
<div style="text-align: justify;">
A SSH tunnel consists of an encrypted tunnel created through a SSH protocol<br />
connection. A SSH tunnel can be used to transfer unencrypted traffic over a<br />
network through an encrypted channel. For example we can use a ssh tunnel to<br />
securely transfer files between a FTP server and a client even though the FTP<br />
protocol itself is not encrypted. SSH tunnels also provide a means to 
bypass firewalls that prohibits or filter certain internet services. For
 example an organization will block certain sites using their proxy 
filter. But users may not wish to have their web traffic<br />
monitored or blocked by the organization proxy filter. If users can connect to<br />
an external SSH server, they can create a SSH tunnel to forward a given port on<br />
their local machine to port 80 on remote web-server via the external SSH<br />
server. I will describe this scenario in detail in a little while.</div>
<div style="text-align: justify;">
To set up a SSH tunnel a given port of one machine needs to be forwarded (of<br />
which I am going to talk about in a little while) to a port in the other<br />
machine which will be the other end of the tunnel. Once the SSH tunnel has been<br />
established, the user can connect to earlier specified port at first machine to<br />
access the network service.</div>
<h3 style="text-align: justify;">
Port Forwarding</h3>
<div style="text-align: justify;">
SSH tunnels can be created in several ways using different kinds of port forwarding<br />
mechanisms. Ports can be forwarded in three ways.</div>
<ol style="text-align: justify;">
<li>Local port forwarding</li>
<li>Remote port forwarding</li>
<li>Dynamic port forwarding</li>
</ol>
<div style="text-align: justify;">
I didn’t explain what port forwarding is. I found Wikipedia’s definition more explanatory.</div>
<blockquote>
Port forwarding or port mapping is a name given to the combined technique of<br />

<ol>
<li>translating the address and/or port number of a packet to a new destination</li>
<li>possibly accepting such packet(s) in a packet filter(firewall)</li>
<li>forwarding the packet according to the routing table.</li>
</ol>
</blockquote>
<div style="text-align: justify;">
Here the first technique will be used in 
creating an SSH tunnel. When a client application connects to the local 
port (local endpoint) of the SSH tunnel and transfer data these data 
will be forwarded to the remote end by translating the host and port 
values to that of the remote end of the channel.</div>
<div style="text-align: justify;">
So with that let’s see how SSH tunnels can be created using forwarded ports with an examples.</div>
<h3 style="text-align: justify;">
Tunnelling with Local port forwarding</h3>
<div style="text-align: justify;">
Let’s say that yahoo.com is being blocked using a proxy filter in the University.<br />
(For the sake of this example. :d  
 . Cannot think any valid reason why yahoo would be blocked). A SSH 
tunnel can be used to bypass this restriction. Let’s name my machine at 
the university as ‘work’ and my home machine as ‘home’. ‘home’ needs to 
have a public IP for this to work. And I am running a SSH server on my 
home machine. Following diagram illustrates the scenario.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjtLy_3wO0wN4-FfOEILVU-T6Zktxde4L7G4e0SBO6McYJuEOghSb1lz5xN8fiNQe69yd50bdpVbryH6fzQ27rTqsYL-4NJ7ieiVKRaBPJmNY_X4LowMl0tBNWk_5yb4MhUuPOfXewsZK6B/s1600/scenario.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="184" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjtLy_3wO0wN4-FfOEILVU-T6Zktxde4L7G4e0SBO6McYJuEOghSb1lz5xN8fiNQe69yd50bdpVbryH6fzQ27rTqsYL-4NJ7ieiVKRaBPJmNY_X4LowMl0tBNWk_5yb4MhUuPOfXewsZK6B/s640/scenario.jpg" width="640" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
 </div>
<div style="text-align: justify;">
To create the SSH tunnel execute following from ‘work’ machine.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -L 9001:yahoo.com:80 home</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
The ‘L’ switch indicates that a local port forward is need to be created. The switch syntax is as follows.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">-L <local-port-to-listen>:<remote-host>:<remote-port></pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
Now the SSH client at ‘work’ will connect
 to SSH server running at ‘home’ (usually running at port 22) binding 
port 9001 of ‘work’ to listen for local requests thus creating a SSH 
tunnel between ‘home’ and ’work’. At the ‘home’ end it will create a 
connection to ‘yahoo.com’ at port 80. So ‘work’ doesn’t need to know how
 to connect to yahoo.com. Only ‘home’ needs to worry about that. The 
channel between ‘work’ and ‘home’ will be encrypted while the connection
 between ‘home’ and ‘yahoo.com’ will be unencrypted.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Now it is possible to browse yahoo.com by visiting <a href="http://localhost:9001/" rel="nofollow">http://localhost:9001</a>
 in the web browser at ‘work’ computer. The ‘home’ computer will act as a
 gateway which would accept requests from ‘work’ machine and fetch data 
and tunnelling it back. So the syntax of the full command would be as 
follows.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -L <local-port-to-listen>:<remote-host>:<remote-port> <gateway></pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
The image below describes the scenario.</div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieF2hNUXvxMcGyDXkvIvdK-vZG1iehwCshQrB_ExTWJmr7zSgH6__ou-IJme_z2fs8Mtr_1MpwFMBkk_70gugglSu_MN8wJhDHgai6Sxp_arriBAgeWyS4SOIFWQI8E0xepJsfILTw8flh/s1600/localportforwarding.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieF2hNUXvxMcGyDXkvIvdK-vZG1iehwCshQrB_ExTWJmr7zSgH6__ou-IJme_z2fs8Mtr_1MpwFMBkk_70gugglSu_MN8wJhDHgai6Sxp_arriBAgeWyS4SOIFWQI8E0xepJsfILTw8flh/s640/localportforwarding.jpg" width="640" /></a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Here the ‘host’ to ‘yahoo.com’ connection is only made when browser makes the<br />
request not at the tunnel setup time.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
It is also possible to specify a port in the ‘home’ computer itself instead of<br />
connecting to an external host. This is useful if I were to set up a VNC session<br />
between ‘work’ and ‘home’. Then the command line would be as follows.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -L 5900:localhost:5900 home (Executed from 'work')</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
So here what does localhost refer to? Is 
it the ‘work’ since the command line is executed from ‘work’? Turns out 
that it is not. As explained earlier is relative to the gateway (‘home’ 
in this case) , not the machine from where the tunnel is initiated. So 
this will make a connection to port 5900 of the ‘home’ computer where 
the VNC client would be listening in.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The created tunnel can be used to 
transfer all kinds of data not limited to web browsing sessions. We can 
also tunnel SSH sessions from this as well. Let’s assume there is 
another computer (‘banned’) to which we need to SSH from within 
University but the SSH access is being blocked. It is possible to tunnel
 a SSH session to this host using a local port forward. The setup would 
look like this.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSDWZrXleJzE0RdHH808w13j6XagYSlDgoQS9xkQKttvaZWmCOm0jWHhAZs9JpMfL3YpokD1zgy8pQgVyMtKCvXWbRyBaT5LQV-iNQQlFUwcNxNC8-Dk0muFCfRUSu87S2oyaSDWPAQbx3/s1600/sshsessionforwarding.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="260" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSDWZrXleJzE0RdHH808w13j6XagYSlDgoQS9xkQKttvaZWmCOm0jWHhAZs9JpMfL3YpokD1zgy8pQgVyMtKCvXWbRyBaT5LQV-iNQQlFUwcNxNC8-Dk0muFCfRUSu87S2oyaSDWPAQbx3/s640/sshsessionforwarding.jpg" width="640" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div style="text-align: justify;">
As can be seen now the transferred data 
between ‘work’ and ‘banned’ are encrypted end to end. For this we need 
to create a local port forward as follows.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -L 9001:banned:22 home</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
Now we need to create a SSH session to local port 9001 from where the session<br />
will get tunneled to ‘banned’ via ‘home’ computer.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -p 9001 localhost</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
With that let’s move on to next type of SSH tunnelling method, reverse tunnelling.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: justify;">
Reverse Tunnelling with remote port forwarding</h3>
<div style="text-align: justify;">
Let’s say it is required to connect to an internal university website from home.<br />
The university firewall is blocking all incoming traffic. How can we 
connect from ‘home’ to internal network so that we can browse the 
internal site? A VPN setup is a good candidate here. However for this 
example let’s assume we don’t have this facility. Enter SSH reverse 
tunnelling..</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
As in the earlier case we will initiate 
the tunnel from ‘work’ computer behind the firewall. This is 
possible since only incoming traffic is blocking and outgoing traffic is
 allowed. However instead of the earlier case the client will now be at 
the ‘home’ computer. Instead of -L option we now define -R which 
specifies<br />
a reverse tunnel need to be created.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -R 9001:intra-site.com:80 home (Executed from 'work')</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
Once executed the SSH client at ‘work’ 
will connect to SSH server running at home creating a SSH channel. Then 
the server will bind port 9001 on ‘home’ machine to listen for incoming 
requests which would subsequently be routed through the created SSH 
channel between ‘home’ and ‘work’. Now it’s possible to browse the 
internal site</div>
<div style="text-align: justify;">
<br />
by visiting <a href="http://localhost:9001/" rel="nofollow">http://localhost:9001</a>
 in ‘home’ web browser. The ‘work’ will then create a connection to 
intra-site and relay back the response to ‘home’ via the created SSH 
channel.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjX9_kvDbHvpW100qg15uiRixRH5DIV_rImXn9Elznas9DZJ8KKNWf6V45WKjpajOKslYgKFa972gfr9QdQMYH0o0RoKelmPeKVNzRdwhfyojUb44Jum7Fjt2HyyplwYIwsXq0K6VrlPr3-/s1600/remoteportforwarding.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="334" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjX9_kvDbHvpW100qg15uiRixRH5DIV_rImXn9Elznas9DZJ8KKNWf6V45WKjpajOKslYgKFa972gfr9QdQMYH0o0RoKelmPeKVNzRdwhfyojUb44Jum7Fjt2HyyplwYIwsXq0K6VrlPr3-/s640/remoteportforwarding.jpg" width="640" /></a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
As nice all of these would be still you 
need to create another tunnel if you need to connect to another site in 
both cases. Wouldn’t it be nice if it is possible to proxy traffic to 
any site using the SSH channel created? That’s what dynamic port 
forwarding is all about.</div>
<h3 style="text-align: justify;">
Dynamic Port Forwarding</h3>
<div style="text-align: justify;">
Dynamic port forwarding allows to 
configure one local port for tunnelling data to all remote 
destinations. However to utilize this the client application connecting 
to local port should send their traffic using the SOCKS protocol. At the
 client side of the tunnel a SOCKS proxy would be created and the 
application (eg. browser) uses the SOCKS protocol to specify where the 
traffic should be sent when it leaves the other end of the ssh tunnel.</div>
<div style="text-align: justify;">
<br /></div>
<pre class="brush: xml; title: ; notranslate" title="">ssh -D 9001 home (Executed from 'work')</pre>
<pre class="brush: xml; title: ; notranslate" title=""> </pre>
<div style="text-align: justify;">
Here SSH will create a SOCKS proxy listening in for connections at local port<br />
9001 and upon receiving a request would route the traffic via SSH channel<br />
created between ‘work’ and ‘home’. For this it is required to configure the<br />
browser to point to the SOCKS proxy at port 9001 at localhost.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgL8nOMmO4XSZI_R1t3B2uf8UwY4WfIG6HCRs1ucG2vkqps0YlQeKe-O2JrDSEsypouxLFAPpBPbcF6cBj9_QwZMoY3sSxlx3lcUdbm_4NyqgRvfRmpxIbBrFw-njRo55KbcNkpERXoTR6h/s1600/dynamicportforwarding.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgL8nOMmO4XSZI_R1t3B2uf8UwY4WfIG6HCRs1ucG2vkqps0YlQeKe-O2JrDSEsypouxLFAPpBPbcF6cBj9_QwZMoY3sSxlx3lcUdbm_4NyqgRvfRmpxIbBrFw-njRo55KbcNkpERXoTR6h/s640/dynamicportforwarding.jpg" width="640" /></a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
thats all hope you enjoy this tutorial   :>)    </div>
</div>

SSH Tunneling Explained

Recently I wanted to set up a remote desktop sharing session from home pc to my laptop. While going through the set up guide I came acro...

DNS poisoning - EXPLANATION | hacking trick

Admin Jixxi 0 5 things a Beginner Hacker should know, BEGINNERS, DNS poisoning, EXPLANATION, EXPLANATION ABOUT, hacking

<div dir="ltr" style="text-align: left;" trbidi="on">
<div dir="ltr" style="text-align: left;">
<span style="font-family: "Courier New",Courier,monospace;"><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">DNS poisoning is a technique that tricks a DNS</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">server into believing that is has received authentic</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">inforamtion when, in reality, it has not. It results in</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">substitution of a false Ineternet provider address at</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">the domain name service level where web addresses</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">are converted into numeric internet provider</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">addresses. It allows attacker to replace IP address</span><br style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;" /><span style="background-color: white; color: #333333; font-size: 13px; line-height: 18px;">DNS entries for a target site on a given DN</span><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">S server<br />with IP addresses of the server he/she controls.<br />Attacker can create fake DNS entries for files with<br />same names as that of target server.<br />The DNS provides a way for computers to translate<br />the domain names we see to the physical IPs they<br />represent. When you load a webpage, your browser<br />will ask its DNS server for the IP of the host you<br />requested, and the server will respond. Your browser<br />will then request the webpage from the server with<br />the IP address that the DNS server supplied.<br />To launch a DNS poisoning attack, follow these<br />steps:</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;"><br />+ set up a fake website on your computer</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;"><br />+ Install treewalk and modify the file mentioned in<br />the readme.txt to your IP address. Treewalk will<br />make you the DNS server.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ Modify the file dns-spoofing.bat and replace the IP<br />address with your IP address.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;"><br />+ Trojanize the dns-spoofing.bat file and send it</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ When the host clicks the Trojanned file, it will<br />replace DNS-entry in her TCP/IP properties to that of<br />your machine.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ You will become the DNS server and her DNS<br />requests will go through you<br />There are four types of DNS poisoning attacks using<br />which you can compromise the target system:</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ Intranet DNS spoofing (local network)<br />When an attacker performs DNS poisoning on a locl<br />area network (LAN), it is called intranet DNS<br />spoofing. An attacker can perform intranet DNS<br />spoofing attack with the help of the ARP poisoning<br />technique. THis is usually conducted on a swithced<br />LAN. To perform this attack, you must be connected<br />to the LAN and be able to sniff the traffic or packets.<br />Once the attacker succeds in sniffing the ID of the<br />DNS request from the intranet, he or she can send a<br />malicious reply to the sender before the actual DNS<br />server.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ Internet DNS spoofing (remote network)<br />Internet DNS poisoning is also known as remote<br />DNS poisoning. This attack can be performed either<br />on asingle or multiple victims anywhere in the world.<br />In order to perform this attack, you need to set up a<br />rouge DNS server with a static IP address.<br />Internet DNS spoofing is performed when the<br />victim's system is connedted to the Internet. It is<br />done with the help of Trojans. It is one of the MITM<br />types of attacks, where the attacker changers the<br />primary DNS entries of the victim's computer. The<br />attacker replaces the victim's DNS IP address with<br />the fake IP address that refers t the attacker's<br />system; thus all traffic will be redirected to the<br />attacker's machine. Now the aatcker can easily sniff<br />the victim's confidential information.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ Proxy server DNS poisoning<br />In the proxy server DNS posoning technique, tha<br />taattacker changes the proxy server setting of the<br />victim to that of the attacker. This is done with the<br />help of a Trojan. This redirects the victim's request<br />to the attacker's fake website where the attacker can<br />sniff the confidential information of the victim.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">+ DNS cache poisoning<br />The DNS system uses cache memory to hold the<br />recently resolved domain names. It is populated<br />with recently used domain names and respective IP<br />address entries. When the user request comes, the<br />DNS resolver first checks the DNS cache; if the<br />domain name that the user requested is found in the<br />cache, then the resolver sends its respective IP<br />address quickly. Thus, it redueces the traffic and<br />time of DNS resolving.<br />Attacker target this DNS cache and make changes or<br />add entries to the DNS cache. The attacker replaces<br />the user-requested IP address with the fake IP<br />address. Then, after when user requests that domain<br />name, the DNS resolver checks the entry in the DNS<br />cache and picks the matched entry. Thus, the victim<br />is rediirected to the attacker's fake server instead of<br />the authorized server.</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;"><br /></span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">How to defend against DNS spoofing:</span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;"><br /></span></span>
<span style="font-family: "Courier New",Courier,monospace;"><span class="text_exposed_show" style="background-color: white; color: #333333; display: inline; font-size: 13px; line-height: 18px;">Resolve all DNS queries to local DNS servers<br />Block DNS requests from going to external severs<br />Implement DNSSEC<br />Configure the DNS resolver to use a new random<br />source prot from its available range for each<br />outgoing query<br />Configure the firewall to restrict external DNS lookup<br />Restrict the DNS recuring service, either full or<br />partial, to authorized users<br />Use DNS Non-Existent Domain rate limitng<br />Secure your internal machines<br />Implement IDS and deploy it correctly<br />Use static ARP and IP table<br />Use SSH encryption<br />Use sniffing detection tools<br />Do not open suspicious files<br />Always use trusted proxy sites<br />Audit your DNS server regularly to remove<br />vulnerabilities</span></span></div>
</div>