Free barracuda proxies software for linux

GNU Proxyknife (formerly known as phc or proxy hunter customed) is a program to validate free proxies for LAN users to reach the Internet by bypassing ISP proxies with strict limits. GNU Proxyknife can be customized to change headers (such as User_Agent) in test requests sent to free proxies.
You can also customize it with your own checksite, checksite port, or checksite key, switch between the CONNECT and GET method, etc., to test and filter free proxies. It can be used to validate free socks5 proxies with a connect command, socks4 proxies with a connect command or free HTTP proxies with a GET or CONNECT method. It can validate free proxies with a TCP tunnel.
Enhancements:
- Myproxy can be a SOCKS4 tunnel.
- This release adds an option "-C", keyword "checkreqin" to enable customizable requests.
- It is possible to implement new protocols (e.g. search MSN proxy).
- Checksite is supported in other protocols (such as ftp://) for HTTP proxies with the GET method.
- This release can be invoked without a startup file.
- Configuring and invoking is simple.
- The output format has been reordered.
- The record of the final request is added to the output.
- The manual has been rewritten.
- Some advanced usages are provided.
- The Chinese translation has been updated.
- Man is integrated into proxyknife.texi.
- Some memory bugs have been fixed.

Bypass Proxy Client is the complete network privacy tool. It ensures absolute privacy wherever you maybe, preventing would-be snoopers from monitoring your surfing, email, or chatting activity. You can bypass blocking filters, firewalls, and proxies. Surf, chat, read news boards, and get all your email at work, on campus (or in regions/areas that may block controversial websites).
Main features:
- Surf the internet using your own virtual network across the web.
-
- Anonymously surf news groups, chat rooms, and web sites!
-
- Protect your Kazaa Identity; Guard against IP tracing -- the no. 1 method
- used by the RIAA to spy on users of file shares (Kazaa, BearShare, etc.)
-
- Prevent corporate networks from eavesdropping and viewing your personal information!
-
- Keep your email and other personal documents private.
-
- Regain access to sites that were previously blocked or filtered. Chat with friends online without concerns about eavesdropping.

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

The Zaval Proxy Suite is an easy-to-use solution that allows monitoring TCP-based protocols, such as HTTP, NNTP and others. It is extremely useful in software development and can be used as a debug tool. Another area of appliance is multiple connections logging with proxy facilities. As soon as its a pure java solution it can be used almost everywhere.

The Zaval Proxy functions as a proxy and transfers data between the server and the client writing incoming and outgoing traffic into log files. So you can see these raw data as is.

On start the Zaval Proxy Suite goes through configuration file and creates the specified number of proxy servers and the shutdown server.

"Proxy server" is a server socket listening on the specified port. When the client is connected proxy connects to the target server and transfers data between them logging entire traffic. On each connection 2 files are created - xxx-input (request data from the client) and xxx-output (response data from the server). The "xxx" means here the sequential number of the connection for the proxy server. The traffic is logged into the separate directory for each proxy.

Shutdown server is needed to close all open connections correctly and close the program.

So, in the particular case you should specify address of proxy server in client application (web browser, for example) and address of the target server in the proxy configuration file. You can create any number of proxy servers that run at the same time, however, they should use different port numbers.

YAZ Proxy application is highly configurable and can be used in a number of different applications, ranging from debugging Z39.50-based applications and protecting overworked servers, to improving the performance of stateless WWW/Z39.50 gateways.
Main features:
- Configurable logging
- SRU/SRW server function, to allow any Z39.50 server to also support the ZiNG protocols
- Load balancing across multiple backend servers
- Session-sharing and pre-initialization to improve performance in servers with expensive session initialization
- Configurable request filtering, to keep bad requests from reaching the server
- XML support -- MARC records can be converted to MARCXML, and XSLT-transformations allow the proxy to support arbitrary retrieval schemas in XML
- Load governor function limits requests from aggressive batch-mode clients
- Efficient multiplexing software enables small memory footprint and very high performance
NOTE: The YAZ Proxy, a complete application, is available under the GPL license. Other licensing terms are available to commercial vendors upon request.

Apache::ProxyConf is a Perl module that can generate proxy configuration for browsers.

SYNOPSIS

# In httpd.conf:

< Location / >
SetHandler perl-script
PerlHandler Apache::ProxyConf
PerlSetVar ProxyConfConfig "/some/location/proxyconf.ini"
< /Location >

The Apache::ProxyConf is used to configure the proxy settings in browsers automatically. The modules returns a script that conforms to the Navigator Proxy Auto-Config File Format. The module is suitable for large scale installations that have multiple (cascading) proxies. It can be used to return the closest proxy based on the network topology. Failover and load distribution is also provided.

Browser configuration

The (virtual) webserver must be entered in the Autoconfigure URL of the browser to make use of the ProxyConf script.

http://proxyconf.some.domain/

In IE the URL must be specified in the Address field, just below the Use automatic configuration script tickbox.

THE CONFIGURATION FILE

The ProxyConf module first reads a .ini-style configuration file to determine the proxy settings of the network. The configuration file contains three sections: proxy, noproxy and https.

The proxy section

The sections proxy and https have an identical format. They contain lines of the form subnet=proxyip:port.

Single proxy

[proxy]
172.16.32.0/20=172.16.32.10:3128

The subnet 172.16.32.0/20 has a single proxy defined. The proxy server is 172.16.32.10 and it listens on port 3128.

Multiple proxies

[proxy]
172.16.0.0/20=172.16.0.10:3128,172.16.0.20:3128

Multiple proxy servers are defined in a comma separated list. In this example clients in the 172.16.0.0/20 subnet use 172.16.0.10 as their primary proxy server. When this server becomes unavailable, the clients will move over to 172.16.0.20 for their proxy requests.

Multiple proxies with load distribution

[proxy]
172.16.0.0/20=(172.16.0.10:3128,172.16.0.20:3128)

When proxy servers are placed between brackets, the load is distribution amongst the proxies. Some clients will have the first proxy as primary and some clients will have the second proxy as primary. The other proxy is used as a backup. The order in which the proxies are tried depends on the IP address of the client. The script is deterministic, so for a given IP address the priority list is always the same.

To determine the proxy list for a given IP address multiple rules may be applied. Subnets are tried from the highest to the lowest mask. The module puts all proxies that are found in a list.

The noproxy section

The noproxy section contains hosts that should be contacted by the clients directly. Noticeably, web servers that use NTLM authentication will not work when clients connect to them via a proxy server. The syntax for specifying noproxy hosts is subnet=fqhn1,fqhn2,... Alternatively, the multiline syntax can be used, as shown in this example.

[noproxy]
0.0.0.0/0=<<less