Windows proxychains


ProxyChains + Tor Backtrack 5 R3 Tutorial

To remain anonymous is one of the important aspect of Information Security, if you want to conduct penetration testing on a remote computer then active connection is required which surely reveal your identity, sometimes you need to hide your identity while doing vulnerability assessment because of your anonymity and security. Proxy Chaning is a concept which is very helpful to hide an identity on the Internet.

What is Proxy Chaining?

Your Computer → Proxy Server → Target Computer

Proxy Concept

The concept mentioned above is the concept of simple proxy, when a user uses one proxy server to hide his/her identity.

Your Computer → Proxy Server 1 +.......+ Proxy Server N → Target Computer

Proxy Chains

Now the usage of multiple proxies at a time is called Proxy Chaining, it is reliable in-terms to hide the identity. In simple words

“Proxy Chaning is the process to use multiple proxies in chain.”

What is Proxy Chains?

The basic concept of proxy chaining is discussed now in this section we will discuss the practical aspect of Proxy Chaining, Proxy Chains (ProxyChains) is an open source program which allows you to make TCP and DNS connection by using proxy for example TOR.

TOR is not necessary for proxychains, you may use any SOCKS 4, SOCKS 5 and HTTPS proxy. There are so many advantages of Proxy Chains for example:

Proxy Chains Tutorial

Proxy Chaining can be achieved on Windows OS too but in this section I will discuss Linux Backtrack, you may use any Linux distribution including Ubuntu.

In Backtrack 5 R3 proxychains is already configured but if you are using any other version of Linux you may download it from official website. Follow the command mentioned below to get proxychains via terminal.

Now the second step is to configure proxychains, there are two options that can be used whether use nano to edit config file on terminal and the other option is to use your favorite editor, both commands are mentioned below.

--OR--

The second option has been used to discuss this tutorial, you may see that there are three options along with there definitions and usage.

  • Dynamic Chain

  • Strict Chain

  • Random Chain

ProxyChains Configuration

Delete # from the front of technique that you want to use, its time to get some proxies. Private and highly anonymous proxies work best (if you can afford) otherwise use the publicly available proxies.

Do not delete the last line, add your proxy list after this line.

Proxy Chains Configuration

Dynamic chain is very good if you are using publicly available proxies.

 

Proxy Chains usage is very simple (proxychains <prog> [args]) [email protected]:~# proxychains nmap ehacking.net[email protected]:~# proxychains firefox[email protected]:~# proxychains msfconsole[email protected]:~# proxychains telnet 192.168.1.1 Example:
Proxy Chaining
 This tutorial completely demonstrate the basic concept and usage of Proxy Chaining and Proxy Chains, if you have any question then feel free to ask on the comment box.  Note: If you want to learn more about Linux and Windows based Penetration testing, you might want to subscribe our RSS feed and Email Subscription  or become our Facebook fan! You will get all the latest updates at both the places.

www.ehacking.net

Proxychains for windows 10 Search

www.infolinks.top

proxy - Proxychains equivalent for Windows? - Server Fault

Link: https://serverfault.com/questions/541279/proxychains-equivalent-for-windows  Verified

Site links: serverfault.com » Who's Domain : serverfault.com » Hosting Provider: serverfault.com

Domain: serverfault.com / IP Server: 151.101.1.69 / United States

How to Use Proxychains to Run Applications Behind …

Link: https://fossbytes.com/how-to-use-proxychains-to-run-applications-behind-proxy/  Verified

Site links: fossbytes.com » Who's Domain : fossbytes.com » Hosting Provider: fossbytes.com

Domain: fossbytes.com / IP Server: 104.28.9.84 / United States

Proxychains Alternatives and Similar Software ...

Link: https://alternativeto.net/software/proxychains/  Verified

Site links: alternativeto.net » Who's Domain : alternativeto.net » Hosting Provider: alternativeto.net

Domain: alternativeto.net / IP Server: 104.25.15.32 / United States

ProxyChains - HTTP and SOCKS download | SourceForge.net

Link: https://sourceforge.net/projects/proxychains/  Verified

Site links: sourceforge.net » Who's Domain : sourceforge.net » Hosting Provider: sourceforge.net

Domain: sourceforge.net / IP Server: 216.34.181.60 / United States

Browse

Link: https://sourceforge.net/directory  Verified

Site links: sourceforge.net » Who's Domain : sourceforge.net » Hosting Provider: sourceforge.net

Domain: sourceforge.net / IP Server: 216.34.181.60 / United States

Development

Link: https://sourceforge.net/directory/development/  Verified

Site links: sourceforge.net » Who's Domain : sourceforge.net » Hosting Provider: sourceforge.net

Domain: sourceforge.net / IP Server: 216.34.181.60 / United States

Internet

Link: https://sourceforge.net/directory/internet/  Verified

Site links: sourceforge.net » Who's Domain : sourceforge.net » Hosting Provider: sourceforge.net

Domain: sourceforge.net / IP Server: 216.34.181.60 / United States

Use proxychains in terminal Ubuntu | Windows 10 Forums

Link: http://jordanhardware.com/threads/use-proxychains-in-terminal-ubuntu.404654/  Verified

Site links: jordanhardware.com » Who's Domain : jordanhardware.com » Hosting Provider: jordanhardware.com

Domain: jordanhardware.com / IP Server: 192.163.221.46 / United States

Other OS

Link: http://jordanhardware.com/.#other-os.68  Verified

Site links: jordanhardware.com » Who's Domain : jordanhardware.com » Hosting Provider: jordanhardware.com

Domain: jordanhardware.com / IP Server: 192.163.221.46 / United States

Ubuntu Forums

Link: http://jordanhardware.com/forums/ubuntu-forums.71/  Verified

Site links: jordanhardware.com » Who's Domain : jordanhardware.com » Hosting Provider: jordanhardware.com

Domain: jordanhardware.com / IP Server: 192.163.221.46 / United States

Proxychains Alternatives for Windows - AlternativeTo.net

Link: https://alternativeto.net/software/proxychains/?platform=windows  Verified

Site links: alternativeto.net » Who's Domain : alternativeto.net » Hosting Provider: alternativeto.net

Domain: alternativeto.net / IP Server: 104.25.14.32 / United States

How to Proxy Chains - Tutorial - YouTube

Link: http://www.youtube.com/watch?v=kt_C9RW_ttA  Verified

Site links: www.youtube.com » Who's Domain : www.youtube.com » Hosting Provider: www.youtube.com

Domain: www.youtube.com / IP Server: 216.58.195.238 / United States

iProxyEver proxychain - Download

Link: https://iproxyever-proxychain.en.softonic.com/  Verified

Site links: iproxyever-proxychain.en.softonic.com » Who's Domain : iproxyever-proxychain.en.softonic.com » Hosting Provider: iproxyever-proxychain.en.softonic.com

Domain: iproxyever-proxychain.en.softonic.com / IP Server: 46.28.209.62 / Spain

tcpcrypt/INSTALL-Windows.markdown at master · scslab ...

Link: https://github.com/scslab/tcpcrypt/blob/master/INSTALL-Windows.markdown  Verified

Site links: github.com » Who's Domain : github.com » Hosting Provider: github.com

Domain: github.com / IP Server: 192.30.255.113 / United States

BIND Open Source DNS Server | Internet Systems …

Link: https://www.isc.org/downloads/bind/  Verified

Site links: www.isc.org » Who's Domain : www.isc.org » Hosting Provider: www.isc.org

Domain: www.isc.org / IP Server: 149.20.64.69 / United States

How to Use Proxychains to Redirect Traffic Through Proxy Server

Sometimes we installed a proxy server, but only certain programs such as Firefox and Google chrome provide proxy settings. Luckily, we can use a command line utility called proxychains to redirect any program to go through our proxy server. This tutorial will show you how to set it up on Debian, Ubuntu, OpenSUSE, Fedora, CentOS/Redhat, Arch Linux and their derivatives.

If your don’t know how to set up a proxy server, then check out this post to learn the merits of shadowsocks proxy. After that, come back here.

Install proxychains

Debian/Ubuntu/Linux Mint/Elementary OS

sudo apt-get install proxychains

OpenSUSE Leap 42.1

proxychains is available from the packman repository.

sudo zypper install proxychains

Fedora

sudo dnf install proxychains

CentOS/Redhat

sudo yum install proxychains

Archlinux

sudo pacman -S proxychains-ng

On kali linux, proxychains is installed by default.

Add a Proxy Server to Proxychains

Open the configuration file.

sudo nano /etc/proxychains.conf

At the end of the file, add your proxy like this

socks5   127.0.0.1   1080

socks5 is the proxy type, you can add other types as well such as http, https, socks4 etc. depending on your situation. 127.0.0.1 is the proxy host, and 1080 is the port on which proxy server listens. Again, change them to your specific situation.

The default proxy is socks4 127.0.0.1 9050 which you can safely remove.

Set a Default DNS Server

It’s highly recommended that you change the default 4.4.2.2 DNS server to something else, such as Google’s DNS server 8.8.8.8/8.8.4.4. Or OpenDNS server 203.67.222.222/203.67.220.220. Open the resolv configuration file.

Debian/Ubuntu

sudo nano /usr/lib/proxyresolv

Linux Mint/Elementary OS

sudo nano /usr/lib/proxychains3/proxyresolv

Fedora/CentOS/Redhat/OpenSUSE

sudo nano /usr/bin/proxyresolv

Find the following line

DNS_SERVER=4.4.2.2

Change its value to something like 8.8.8.8. Then save and close the file. On Arch Linux, there’s no proxyresolv config file.

Test

Just prepend proxychains to any command you execute like the following.

proxychains youtube-dl -citw https://www.youtube.com/channel/<channel-id>

If you are using youtube-dl then you may know that it has not built-in support for socks proxy, but Proxychains will redirect youtube-dl to go through the proxy server.

If you want to redirect all your terminal traffic through proxy server, then enter start a new shell program with proxychains, like below.

proxychains bash

This command will start another bash shell with proxychains in your terminal and from now on you don’t have to prepend proxychains to your command. Your traffic in this new shell will be automatically redirected through proxy server.

Note:  Terminal is different from shell. Terminal is the device that enable you to connect to a host computer whereas shell is a piece of software on the host computer. Shell is a command line interpreter, translating your command to zeros and ones so the computer can understand your command. When a terminal connects to a host computer, a shell program will be automatically started so that the user’s commands can be interpreted by the shell and the computer can understand the user’s commands.

Quiet Mode

By default, proxychains will output its activity to the terminal. If you don’t want to see this information, then you can disable it by editing /etc/proxychains.conf file.

sudo nao /etc/proxychains.conf

Find the following line

#quiet_mode

Remove the hashtag. Save and close the file. Now you will only see the output of the application that is being redirected.

As always, if you found this post useful, please subscribe to our free newsletter or follow us on Google+, Twitter or like our Facebook page

Rate this tutorial

[Total: 15 Average: 3]

www.linuxbabe.com

Proxychains - Redirect All Your Connections

ProxyChains is a UNIX program, that hooks network-related libc functions in DYNAMICALLY LINKED programs via a preloaded DLL (dlsym(), LD_PRELOAD) and redirects the connections through SOCKS4a/5 or HTTP proxies.

It supports TCP only (no UDP/ICMP etc).

The way it works is basically a HACK; so it is possible that it doesn’t work with your program, especially when it’s a script, or starts numerous processes like background daemons or uses dlopen() to load “modules” (bug in glibc dynlinker). It should work with simple compiled (C/C++) dynamically linked programs though. 

If your program doesn’t work with proxychains, consider using an iptables based solution instead; this is much more robust.

Supported Platforms: Linux, BSD, Mac.

This program can be used to circumvent censorship. Doing so can be VERY DANGEROUS in certain countries.

ALWAYS MAKE SURE THAT PROXYCHAINS WORKS AS EXPECTED BEFORE USING IT FOR ANYTHING SERIOUS.

This involves both the program and the proxy that you’re going to use. For example, you can connect to some “what is my ip” service like ifconfig.me to make sure that it’s not using your real ip.

ONLY USE PROXYCHAINS IF YOU KNOW WHAT YOU’RE DOING

Installation

needs a working C compiler, preferably gcc

./configure --prefix=/usr --sysconfdir=/etc make [optional] sudo make install [optional] sudo make install-config (installs proxychains.conf)

If you choose not to install, you can use proxychains from the build directory like this:

./proxychains4 -f src/proxychains.conf telnet google.com 80

When to use it ?

  1. When the only way to get “outside” from your LAN is through proxy server.
  2. To get out from behind restrictive firewall which filters outgoing ports.
  3. To use two (or more) proxies in chain:like: your_host <–> proxy1 <–> proxy2 <–> target_host
  4. To “proxify” some program with no proxy support built-in (like telnet)
  5. Access intranet from outside via proxy.
  6. To use DNS behind proxy.
  7. To access hidden tor onion services.

Some cool features:

  • This program can mix different proxy types in the same chain like:your_host <–>socks5 <–> http <–> socks4 <–> target_host
  • Different chaining options supported random order from the list ( user defined length of chain ). exact order (as they appear in the list ) dynamic order (smart exclude dead proxies from chain)
  • You can use it with most TCP client applications, possibly even network scanners, as long as they use standard libc functionality. pcap based scanning does not work.
  • You can use it with servers, like squid, sendmail, or whatever.
  • DNS resolving through proxy.

Configuration:

proxychains looks for config file in following order:

  1. file listed in environment variable PROXYCHAINS_CONF_FILE or provided as a -f argument to proxychains script or binary.
  2. ./proxychains.conf
  3. $(HOME)/.proxychains/proxychains.conf
  4. $(sysconfdir)/proxychains.conf **

** usually /etc/proxychains.conf

Proxychains Example:

$ proxychains telnet targethost.com

in this example it will run telnet through proxy(or chained proxies) specified by proxychains.conf

$ proxychains -f /etc/proxychains-other.conf targethost2.com

in this example it will use different configuration file then proxychains.conf to connect to targethost2.com host.

$ proxyresolv targethost.com

in this example it will resolve targethost.com through proxy(or chained proxies) specified by proxychains.conf

 

Source && Download

n0where.net

Proxify applications with tsocks and proxychains on ubuntu

Tsocks

There are many network applications that do not have the option to specify a proxy or do not support the use of proxies. In such cases tsocks is a useful tool to wrap all network communication done by a program via a socks proxy.

Project websitehttp://tsocks.sourceforge.net/

Install on ubuntu

$ sudo apt-get install tsocks

Now open the configuration file /etc/tsocks.conf and edit the following parameters

1. server2. server_type3. server_port

Sample file

# This is the configuration for libtsocks (transparent socks) # Lines beginning with # and blank lines are ignored # # The basic idea is to specify: # - Local subnets - Networks that can be accessed directly without # assistance from a socks server # - Paths - Paths are basically lists of networks and a socks server # which can be used to reach these networks # - Default server - A socks server which should be used to access # networks for which no path is available # Much more documentation than provided in these comments can be found in # the man pages, tsocks(8) and tsocks.conf(8) # Local networks # For this example this machine can directly access 192.168.0.0/255.255.255.0 # (192.168.0.*) and 10.0.0.0/255.0.0.0 (10.*) local = 192.168.0.0/255.255.255.0 local = 10.0.0.0/255.0.0.0 # Paths # For this example this machine needs to access 150.0.0.0/255.255.0.0 as # well as port 80 on the network 150.1.0.0/255.255.0.0 through # the socks 5 server at 10.1.7.25 (if this machines hostname was # "socks.hello.com" we could also specify that, unless --disable-hostnames # was specified to ./configure). path { reaches = 150.0.0.0/255.255.0.0 reaches = 150.1.0.0:80/255.255.0.0 server = 10.1.7.25 server_type = 5 default_user = delius default_pass = hello } # Default server # For connections that aren't to the local subnets or to 150.0.0.0/255.255.0.0 # the server at 192.168.0.1 should be used (again, hostnames could be used # too, see note above) server = 127.0.0.1 # Server type defaults to 4 so we need to specify it as 5 for this one server_type = 5 # The port defaults to 1080 but I've stated it here for clarity server_port = 9050

After doing this its important to start a socks proxy on port 9050. The best solution is TOR.Download/Install tor and start it.

Now launch any application from the terminal as following

$ tsocks epiphany

Epiphany is a browser. After launching epiphany from tsocks, open ipmango.com to verify your ip address.

So using tsocks any application that uses sockets can be made to use the socks proxy and become anonymous.

Proxychains

Tsocks is limited to socks5 proxy. It cannot use http proxy servers. Here comes the solution for http proxies - proxychain.

Project websitehttp://proxychains.sourceforge.net/

Install on ubuntu

$ sudo apt-get install proxychains

Now edit the configuration file /etc/proxychains.conf

# proxychains.conf VER 3.1 # # HTTP, SOCKS4, SOCKS5 tunneling proxifier with DNS. # # The option below identifies how the ProxyList is treated. # only one option should be uncommented at time, # otherwise the last appearing option will be accepted # #dynamic_chain # # Dynamic - Each connection will be done via chained proxies # all proxies chained in the order as they appear in the list # at least one proxy must be online to play in chain # (dead proxies are skipped) # otherwise EINTR is returned to the app # strict_chain # # Strict - Each connection will be done via chained proxies # all proxies chained in the order as they appear in the list # all proxies must be online to play in chain # otherwise EINTR is returned to the app # #random_chain # # Random - Each connection will be done via random proxy # (or proxy chain, see chain_len) from the list. # this option is good to test your IDS :) # Make sense only if random_chain #chain_len = 2 # Quiet mode (no output from library) #quiet_mode # Proxy DNS requests - no leak for DNS data #proxy_dns # Some timeouts in milliseconds tcp_read_time_out 15000 tcp_connect_time_out 8000 # ProxyList format # type host port [user pass] # (values separated by 'tab' or 'blank') # # # Examples: # # socks5 192.168.67.78 1080 lamer secret # http 192.168.89.3 8080 justu hidden # socks4 192.168.1.49 1080 # http 192.168.39.93 8080 # # # proxy types: http, socks4, socks5 # ( auth types supported: "basic"-http "user/pass"-socks ) # [ProxyList] # add proxy here ... # meanwile # defaults set to "tor" #socks5 127.0.0.1 9050 http 127.0.0.1 8080

Comment out proxy_dns option, otherwise it will be difficult to make it work. Then towards the end of the file add the list of proxy servers. Add only 1 and comment the rest of easy use. Over here we first test the http proxy so add the following

http 127.0.0.1 8080

After adding the http proxy to the list its time to start an http proxy server on localhost (127.0.0.1). This can be done by either installing TOR+Polipo or by simply launching the burp suite program which has an integrated http proxy server. Once the http proxy server is up, launch proxychains along with the application that needs to be proxified :

$ proxychains telnet google.com 80

This will make the telnet program use the http proxy specified earlier. Simple and effective.

It should be clearly understood that tsocks or proxychains are not proxy servers, they are just proxifying tools that can make non proxy aware programs to communicate via proxies.

Last Updated On : 15th August 2012

www.binarytides.com

Download ProxyCap

www.proxycap.com

 
 
     
 
Windows
   
  ProxyCap version 5.29  30-day trial
   
  pcap529_x86.msi  4.36 MB (for Windows 10/8.1/8/7/Vista/XP/2000, Server 2008/2003)
   
  pcap529_x64.msi  5.88 MB (for the x64 editions of Windows 10/8.1/8/7/Vista/XP, Server 2012/2008/2003)
   
   
 
  Mac
   
  ProxyCap version 2.18  30-day trial
   
  proxycap_2.18.dmg  4.06 MB (for Mac OS X 10.4.11-10.13 Intel/PowerPC)
   
   
 
  Windows Mobile
   
  ProxyCap version 1.43  14-day trial
   
  pcap143_arm.cab  123 K (for Windows Mobile 5 Pocket PC, Windows Mobile 6, 6.1, 6.5 Professional/Classic)
   
   

© 2016, Proxy Labs. All rights reserved.

How to Evade Detection Using Proxychains « Null Byte :: WonderHowTo

Welcome back, my novice hackers!

The worst thing that can happen to any hacker is being detected by a security admin, the security technologies (IDS, firewall, etc.), or a forensic investigator.

Every time we send a packet to our intended target, that packet contains our IP address in the IP header. When we make a TCP connection, the target system will log our IP address as it logs all connections. If we set off any security alarms or alerts, our IP address will be logged. All of these events increase the possibility of detection.

In order to hack anonymously with the least chance of detection, we need to use an intermediary machine whose IP address will be left on the target system. This can be done by using proxies.

These systems are designed to accept our traffic and then forward it on to the intended target. Of course, the proxy will likely log our traffic, but an investigator would have to get a subpoena or search warrant to obtain the logs.

If we string multiple proxies in a chain, we make it harder and harder to detect our original IP address. If one of those proxies is outside the jurisdiction of the victim, it makes it very unlikely that any traffic can be attributed to our IP address.

Both Kali and BackTrack have an excellent tool for proxying our traffic called proxychains. In this tutorial, I will show how to use this simple, but powerful tool.

Step 1: Find Proxychains

Let's start by finding proxychains. Type:

  • kali > locate proxychains

As we can see in the screenshot below, proxychains is in the /usr/bin directory. Since /usr/bin is in our PATH variable, we can use it from any directory. This is just as we would want since we use proxychains with other commands, which may NOT likely be in the PATH variable.

Step 2: Proxychains Syntax

The syntax for the proxycahins command is simple and straightforward.

  • kali> proxychains <the command you want proxied> <any arguments>

So, if I wanted to use proxychains to scan a site with nmap anonymously, I could type:

  • kali> proxychains nmap -sS <IP address>

Step 3: Set Up the Config File

Like nearly every application in Linux/Unix, configuration is managed by a simple text file called the config file. In the case of proxychains, this file is /etc/proxychains.conf. We can open it in leafpad or any other text editor (vi, emacs, gedit, kwrite, etc.), by typing:

  • kali > leafpad /etc/proxychains.conf

When we do so, we will see a file like that displayed below. If we scroll down this file a bit, we will see a section that I have highlighted labeled "add proxy list here...".

To get proxychains to use intermediary proxies, we simply need to add the IP addresses of the proxies we want to use here. It's important to note that proxychains defaults to use Tor.

Notice the last line in the screenshot above. It directs proxychains to send the traffic first through our host at 127.0.0.1 on port 9050 (the default Tor configuration). If you are using Tor, leaves this as it is. If you are not using Tor, you will need to comment out this line.

As much as I like Tor, it is very slow and we now know that the NSA has broken Tor, so I am much less likely to depend upon it for anonymity.

Step 4: Let's Test It

Now that we have put a proxy between us and any traffic we send, let's test it out. In this case, I am simply going to do an nmap scan to wonderhowto.com anonymously by sending the scan through a proxy. The command would be as follows:

  • kali > proxychains nmap -sS 8.26.65.101

As you can see in the screenshot above, I have successfully scanned wonderhowto.com through my chosen proxy and returned the results back to me. In this way, it appears that my proxy scanned wonderhowto.com and not my IP address.

Some More Interesting Options

Now that we have proxychains working, let's look at some options that we can configure through the proxychains.conf. As we now have it set up, we are simply using a single proxy. We can put in numerous proxies and use all of them, we can use a limited number from the list, or we can have proxychains change the order randomly. Let's try all of those options.

Step 5: Add More Proxies

First, let's add some more proxies to our list. Open /etc/proxychains.config and add more proxy IPs like I've done below.

Step 6: Proxychaining

Now that we have multiple IPs in our proxychain.conf we can set up dynamic chaining. Dynamic chaining will enable us to run our traffic through every proxy on our list, and if one of the proxies is down or not responding, it will automatically go to the next proxy in the list without throwing an error.

To do so, let's first open the proxychains configuration file again.

With this file open, uncomment out the "dynamic_chains" line. This will enable dynamic chaining of our proxies allowing for greater anonymity and trouble-free hacking.

Step 7: Random Chaining

Finally, we can also use "random chaining". With this option, proxychains will randomly choose IP addresses from our list and use them for creating our proxychain. This means that each time we use proxychains, the chain of proxy will look different to the target, making it harder to track our traffic from its source.

To do so, open the /etc/proxychains.conf file and comment out "dynamic chains" and uncomment "random chain". Since we can only use one of these options at a time, make certain that you comment out the other options in this section before using proxychains.

In addition; you may want to uncomment the line with "chain_len". This will determine how many of the IP addresses in your chain will be used in creating your random proxy chain.

Now that you know how to use proxychains, you can do your hacking with relative anonymity. I say relative, because there is no surefire way to remain anonymous with the NSA spying on all our activity. All we can do is make detection MUCH harder, and proxychains can help do this for us.

Image credits: Glove and keyboard and IP fingerprinting via Shutterstock

null-byte.wonderhowto.com


Смотрите также