Free https proxies software for linux

HTTP Proxy Client is the small set of libraries and scripts, which provides transparent access to Internet via HTTP proxy for programs, which uses TCP/IP for communication.
The list of programs includes: telnet, ftp, licq, cvs, smth else? Project implements dynamic library, that can be preloaded before program run.
The library substitutes some system calls (connect(), gethostbyaddr(), gethostbyname()), with calls, which makes TCP/IP connection through HTTP proxy. This allows client programs behind HTTP proxy work with Internet without limitations.
At the moment tested on i386 Linux, i386/sparc Solaris.
Enhancements:
- While using dotted address, applications will attempt to connect regardless DNS lookup result.

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.

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.

ftp.proxy is an application level gateway for FTP. It sits between a client and a server forwarding command and data streams supporting a subset of the file transfer protocol as described in RFC 959.
But, beside this basic function which makes the program useful on firewall or masqueraders it offers fixing the FTP server (e.g. for connections into a protected LAN) and proxy authentication.
Main features:
- ftp.proxy offers external access control programs (ACP), that is an external program decides if a user can use the proxy service or not. This decision can be made on username, host name, day of time etc.
- Since version 1.0.1 ftp.proxy supports also command control programs. Similar to ACPs the CCPs permit or deny access to certain FTP commands on the server, e.g. its possible to allow a user to get files but to deny any kind of uploads.

Frickin PPTP Proxy is a fast PPTP proxy for any BSD system with the OpenBSD packet filter installed.
It handles bi-directional tunnels transparently and can be chained from one proxy to another over several servers.
Enhancements:
- This release fixes an endian issue with echo IDs that made the proxy unusable for a majority of users.
- There is additional information regarding a pf scrub issue in the documentation.

Japt-Proxy is a JAVA based Caching Proxy for Debians APT-System. Japt-Proxy is very reliable and lightning fast. Japt-Proxy is usually used in environments where several Debian systems have to be kept up-to-date without downloading the same files over and over again from the debian mirrors. Mostly these environments are data centers, Linux-powered companies, schools, public authorities and so on.
Often Japt-Proxy is used because of small sized internet connections but it is also useful to install complete debian systems over the net (read: over the proxy). Even with high volume internet connections Japt-Proxy can dramatically reduce the time to install or update Debian on many machines.
Why Java?
I know there are people out there thinking "Hey? Why Java?". There are a bunch of reasons why people asking those questions. I have a simple answer to all those questions. The answer is, that Java enabled me to easily develop the fastest and most reliable APT-Proxy. Java and the Apache Software Foundation provides such good libraries for this job, that it wasnt very hard to bring up this tool.
If you dont trust, test it - the installation takes less than five minutes!
Doesnt a general proxy server supersede an APT-Proxy?
No, it doesnt. Japt-Proxy knows the characteristics of a Debian archive and their files. It knows, for example, that .deb files wont change, because newer files would have a new name (the version is always part of the filename), hence it wont recheck if there is a newer version of this specific file.
Furthermore you can configure the Japt-Proxy to delete old versions of a package in its cache directory - a general proxy cache would simple delete files that havent been requested for some time.
So, a general caching proxy like Squid is a perfect tool for caching "normal" internet traffic. If you need a proxy for faster APT access - Japt-Proxy is the right tool for you.
Main features:
- Caching of all apt requests from Debian archives
- Multi-threaded architecture which increases the download speed enormously when several machines are requesting packages
- Builds up a partial mirror directory automatically, with exactly the same directory structure and filenames as the original mirror
- Automatic and configurable cache cleanup (purging packages in cache if newer versions exists)
- Makes sources.list configuration easier for multiple machines - if you change your internet backend server you only have to make the change once in Japt-Proxy, instead of on all Debian machines
- Works with multiple architectures
- Backend support for HTTP and FTP
- existing .debs can be copied into the Japt-Proxy cache directory (from a CD or DVD for example) and will be used by the Proxy automatically

Blitzed Open Proxy Monitor or BOPM, is an open source open proxy monitor, designed for use with hybrid-based ircds, although it can be used with slight modification on any server which has the ability to show connects to opers and that supports KLINEs.
BOPM is known to work without modification on the following ircds:
- Bahamut (tested with 1.4.28, 1.4.30)
- Hybrid (tested with 2.8/hybrid-5.3p8, ircd-hybrid-6.3 and ircd-hybrid-7)
- ircd-ratbox (tested with > 2.1.8)
- charybdis (tested with > 2.0.0)
- Unreal (tested with 3.1.2 and 3.2)
- Dancer (tested with 1.0.31)
- TR-IRCD
- IRCu
- Ultimate (tested with UltimateIRCd 2.8.8 and 3.0.0.b3) - please note, earlier versions of Ultimate IRCD are not supported
- LiquidIRCd (tested with 1.0.4)
- InspIRCd (known to work with 1.0 and 1.1 version branches - instructions are given here)
Please note that BOPM will not work with older versions of Unreal without modifying Unreal to send the clients IP address in a connection notice. Patches are also available for download. On the latest versions of Unreal this is no longer needed. Remember for all Unreal versions you must set the perform line correctly (documented in the config file).
How does it work?
When a client connects to the IRC server, BOPM scans the client for open proxies. It then determines whether they are really open by using them to connect back to the server.
How does BOPM improve on first generation scanners (wgmon, tcm, oomon)?
It extends them by adding support for SOCKS4, SOCKS5, WinGate, HTTP proxies, insecure Cisco routers, simultaneous connections, and a more scalable model (written in C). BOPM also has support for a DNS blacklist, similar to MAPS RBL+ or Visi RSL
BOPM is in use without issue on servers receiving over 400 connections per minute during normal real-world operation (as in, regular client load excluding bursts and attacks). That is 7 user connections per second, enough for even the largest of IRC servers.
Additionally, BOPM contains the ability to match hosts against a DNS blacklist such as DroneBL or your own custom list, it can also submit new proxies that are found via email if the list accepts them.
Enhancements:
- This version was fixed to work with GCC 4 and various other cleanups.

IOC::Proxy::Interfaces is a IOC::Proxy subclasss to proxy objects with a given interface.

SYNOPSIS

use IOC::Proxy::Interfaces;

my $proxy_server = IOC::Proxy->new({
interface => AnInterface,
# ... add other config values here
});

$proxy_server->wrap($object);
# our $object is now proxied, but only the
# methods which are part of the interface
# will work, all others will throw exceptions

$object->method_in_interface(); # works as normal

$object->method_not_in_interface(); # will thrown an exception

This is a subclass of IOC::Proxy which allows for the partial proxing of an object. It will only proxy the methods of a given interface, all other methods will throw a IOC::MethodNotFound exception. This could be used to (in a very weird way) emulate the concept of upcasting in Java, it is also somewhat like the idea of using interfaces with Dynamic Proxies in Java as well (see the article link in "SEE ALSO").

This proxy can be useful if you need to have an object strictly conform to a particular interface in a particular situation. The interface class is also pushed onto the proxies @ISA so that it will respond to UNIVERSAL::isa($object, Interface) correctly. Keep in mind that there is no need for the object being proxied to have the interface in its @ISA prior to being proxied. The proxy is dynamic and only requires that the object conform to the interface when it is being wraped but the proxy object.