Free anonymous proxy software for linux

IP::Anonymous is a Perl port of Crypto-PAn to provide anonymous IP addresses.

SYNOPSIS

use IP::Anonymous;
@key = (0..31);
my $object = new IP::Anonymous(@key);
print $object->anonymize("192.0.2.0")."n";

This is a Perl port of Crypto-PAn. Crypto-PAn is a cryptography-based sanitization tool for network trace or log data. The tool has the following properties:

One-to-one

The mapping from original IP addresses to anonymized IP addresses is one-to-one.

Prefix-preserving

The IP address anonymization is prefix-preserving. That is, if two original IP addresses share a k-bit prefix, their anonymized mappings will also share a k-bit prefix.

Consistent across traces

Multiple traces can be sanitized in a consistent way, over time and across locations, even though the traces might be sanitized separately at different time and/or at different locations.

Cryptography-based

To sanitize traces, trace owners provide a secret key. Anonymization consistency across multiple traces is achieved by the use of the same key. The construction of IP::Anonymous preserves the secrecy of the key and the (pseudo)randomness of the mapping from an original IP address to its anonymized counterpart.

This Perl port of Crypto-PAn uses similar logic to that found in Crypto-PAn 1.0, but most importantly maintains consistency in the process so that regardless of implementation, using the same key in each will give consistent results.

USAGE

$object = new IP::Anonymous(@key)

Initializes the electronic codebook object with a 32 8-bit decimal array. This array, consisting of 32 decimals between 0 and 255 inclusive, is the user defined private key for this anonymization session. This 256 bit key should be kept private. The key can be used across sessions to maintain consistent mappings between the original and the anonymized IP addresses.

$object->anonymize($address)

Called with a dotted quad IP address string (e.g. 192.0.2.0). Returns an anonymized version of that IP address as a dotted quad string.

SSL Proxy server listens on a TCP port, accepts SSL connections, and forwards them to another local or remote TCP port.
For example, it is possible to create an HTTPS server if you have an HTTP server and you run an SSL Proxy server on port 443 which forwards the connections to port 80.
SSL Proxys design makes it as secure as possible and still perform well.
Enhancements:
- Improved certificate handling (chained certificates are now supported), more error information on SSL protocol errors during SSL_accept(), -U and -D options (buffer size), and a "powered by" logo.

Wake On LAN proxy allows machines behind a gateway/firewall to be woken up. You have a constant connection to the Internet, but you are away from base. All machines except the gateway are powered off while you are away. Remotely you decide you want to access one of your machines. You need to power it up first. For machines with suitable NICs there is the Wake On LAN mechanism. But this doesnt work over the Internet because you would have to route a packet to your internal network. The firewall stops you from doing that, for good reasons. Even if you were able to route a packet, you wouldnt want this information to travel in the clear, otherwise other people who intercept your packets could learn how to turn on your machines remotely too. So you need some kind of authentication and privacy.

Enter Wake On LAN proxy. This runs on your gateway, or on some other machine on the network thats always on, and can be reached from the Internet by port forwarding. You can send a command to it to wake a particular machine and it broadcasts a suitable packet on the internal network.

tinyproxy is a lightweight HTTP proxy licensed under the GPL. Designed from the ground up to be fast and yet small, it is an ideal solution for sites where a full-featured HTTP proxy is required, but the system resources required to run a more demanding HTTP proxy are unavailable. tinyproxy is fully compatible with all existing web browsers.
Main features:
Anonymous mode
- Allows you to specify which HTTP headers should be allowed through, and which should be blocked - this allows you to restrict both what data comes to your web browser from the HTTP server (eg, cookies), and to restrict what data is allowed through from your web browser to the HTTP server (eg, version information).
Easily modified
- If youre looking to build a custom web proxy, tinyproxy is very easy to modify to your custom needs - the source is straightforward, adhering to the KISS principle. As such, it can be used as a foundation for anything you may need a web proxy to do (send patches!)
Remote monitoring
- Using the remote monitoring feature, you can access proxy statistics from afar, letting you know exactly how busy the proxy is.
Load average monitoring
- tinyproxy can be configured to watch the load average on most platforms, and start refusing requests when the load reaches a certain point - you may recognize this feature from sendmail.
Access control
- You can configure tinyproxy to only allow requests from a certain subnet, or from a certain interface, thus allowing you to ensure that random, unauthorized people will not be using your proxy.
Secure
- With a bit of configuration (specifically, making the log file owned by nobody and running it on a port >1024), tinyproxy can be made to run without any special privileges, thus minimizing the chance of system compromise. Furthermore, it was designed with an eye towards preventing buffer overflows. The simplicity of the code ensures it remains easy to spot such bugs.
Small footprint
- As mentioned above, tinyproxy requires very little in the way of system resources - the memory footprint tends to be around 2MB with glibc, and the CPU load increases linearly with the number of simultaneous connections (depending on the speed of the connection). Thus, tinyproxy can be run on a spare, older machine, or even a workstation, without any noticeable impact on performance.

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.

The Camarades Linux Proxy is a small program that is meant to run on a firewall protecting an internal network. It allows multiple users behind a firewall to use the Camarades Web camera program.

To make it run the following:

1. Edit Makefile to see that everything seems ok.
Make any necessary changes(?).
Default install location for the cama executable is in /usr/local/bin.
2. Build the program by typing
make
3. If everything went well, type
make install
4. Edit camarc and copy it to /etc
5. Start cama
cama

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!