Free socks proxy software for linux

tsocks provides transparent network access through a SOCKS version 4 or 5 proxy (usually on a firewall).

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications dont know how to gain access through SOCKS servers. This means that network based applications that dont understand SOCKS are very limited in networks they can reach. An example of this is simple telnet.

tsocks role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary. If youre on a network firewalled from the internet with a SOCKS server for outside access, telnet cant use this server and thus cant telnet out to the Internet., sou you cannot get out.

tsocks is based on the shared library interceptor concept. Through use of the LD_PRELOAD environment variable or the /etc/ld.so.preload file tsocks is automatically loaded into the process space of every executed program. From there it overrides the normal connect() function by providing its own. Thus when an application calls connect() to establish a TCP connection it instead passes control to tsocks. tsocks determines if the connection needs to be made via a SOCKS server (by checking /etc/tsocks.conf) and negotiates the connection if so (through use of the real connect() function )

Spike Proxy is an open source HTTP proxy for finding security flaws in web sites.

SPIKE Proxy is part of the Spike Application Testing Suite and supports automated SQL injection detection, web site crawling, login form brute forcing, overflow detection, and directory traversal detection.

To Use:

python spkproxy.py [ optional port argument, 8080 is default ]
Then set up your browser to use that port for both HTTP and
HTTPS proxies.

Then watch the traffic go!

Socks via HTTP provides a socks tunnel via HTTP.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.

The SOCKS protocol allows programs to traverse firewalls on any port number and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others.

Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy.

Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection.

Socks via HTTP is 100% Java, and can run on any OS. It is entirely written in Java.

rsh.proxy project is a proxy for rsh, rexec and rlogin.

About rsh

rsh (remote shell) is a command line computer program which can execute shell commands as another user, and on another computer across a computer network. The remote system on which the rsh executes the command needs to be running the rshd daemon. The rsh command shares the same name as another common UNIX utility, the restricted shell, which first appeared in PWB/UNIX; in System V Release 4, the restricted shell is often located at /usr/lib/rsh.

About rlogin

rlogin is a Unix software utility that allows users to log in on another host via a network, communicating via TCP port 513. It was first distributed as part of the 4.2BSD release. rlogin is also the name of the application layer protocol used by the software, part of the TCP/IP protocol suite. Logged-in users can act as if they were physically present at the computer.

Mobile Web Proxy is a (CGI) tool to make more Web pages available from some mobile devices (cell phone Web browsers, etc.).
When I began using my cell phones mobile web browser, one of the things I realized was that there were a lot of web pages that my cell phones web browser simply wouldnt let me see. My shiny new Motorola Razr from T-Mobile, for many pages, would display an error message like "413: Page cannot be displayed." It happened annoyingly often; browsing the web from my cell phone was a lot like trying to read a book or a magazine with large chunks simply ripped out. And when I tried troubleshooting, I might have missed something, but it seemed like a big problem without an easily available solution.
So I tried to provide my own solution. I made a proxy that would present webpages for the mobile web so that they would display in a way that would work for my cell phones web browser. Technologies include paging, tag cleaning, and optional caching to improve performance, but without getting into technical details, this means that I can access some pages on the web that I couldnt access earlier.
Enhancements:
- A bug that caused the script to spuriously report 404 errors was fixed.
- A smaller default page size was set so that tag-rich pages would be rendered in a way more likely to be displayable on mobile Web browsers.

IMAP Proxy server is a caching IMAP proxy server. It was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction.

This behaviour can cause tragic performance problems on the IMAP server. imapproxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs out.

When the webmail client connects again, imapproxy will determine if theres a cached connection available and reuse it if possible.

How does imapproxy keep track of which server connection is for which user?

Upon the first successful login to the real IMAP server (through the proxy), imapproxy fills in a little record that contains the username, an md5 digital signature of the password and the server socket descriptor thats being used.

After you log out and then log back in again, imapproxy just has to find a record that matches your username and password. These records are stored in a hash table (with the username being the hash key) in memory, so the lookups are pretty fast.

Can IMAP Proxy support multiple backend servers?

If you want IMAP Proxy to be able to proxy to multiple backend IMAP servers, you can run multiple instances of IMAP Proxy and make sure each instance is looking at a different configuration file.

Before you do this, take a look at perdition which appears to have been designed with this specific task in mind.