Free list of https proxy servers software for linux

Anon Proxy Server is a fast http, https, socks caching proxy server. Easy web based configuration, optional p2p anonymous mode.
Main features:
- Easy Configuration - Web based, no editing text configuration files.
- Memory - No big databases are kept in memory, no matter how large the cache is, memory usage will only increase when more users access it at the same time.
- Speed - To see how much cpu the proxy uses, run top or task manager. Then open multiple windows and hit reload continously, on my computer I usually run out of bandwidth before it goes near 3-5% cpu usage.
- Shared Cache - Can be used as a general cache for all users of a computer/network instead of one cache per profile.
- Automatic config - Auto generates the .pac file for automatic proxy settings, no more updating in the do not use proxy section of individual users browsers.
- Anonymous P2P proxy - Joining the anonymous proxy network will allow you to use other peoples proxys for browsing and allow them to use yours.
- SOCKS - Supports enough of SOCKS to run ftp, most Instant messengers, irc, limewire, etc.
- User authentication - Supports external user authentication.
Enhancements:
- The program now checks for errors in access configuration.
- Variable timeout values were added.
- Log rotation was fixed.
- Occasional crashes on a bad URL were fixed.
- The auto configuration .pac file was fixed, so it should work even if the proxys URL was not set properly.
- Anon proxy defaults to 3 keys now for more reliability.

Firewall and Proxy Server HOWTO project is designed to describe the basics of firewall systems.

And also to give you some detail on setting up both a filtering and proxy firewall on a Linux based system.

Firewalls have gained great popularity as the ultimate in Internet Security.

Today firewalls are a part of almost every networking device. Like most hot subject they are also often misunderstood.

This HOWTO will go over the basics of what a firewall is and how to set one up.

I am using kernel 2.2.14 and RedHat 6.1 to develop this howto so the examples here are based on this distribution.

If you find differences in your distribution, please email me and Ill update this howto.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

DeniX Server OS is an independent Linux based distribution built from scratch by Denis Salmanovich. They aim to offer a user-friendly full-featured server operating system, pre-configured, well structured and easy to work with, and filled with the latest stable versions of Linux apps.
Its easy to install and configure. Every package is downloaded from the authors source and compiled when installed.
Main features:
- Domain Controller
- ADSL/CABLE Router (PPPoE)
- Network Firewall
- Anti Virus Gateway
- Anti Spam Gateway
- Mail Server (local & external) + Web Mail
- Calendar Sharing Support
- Network File Server
- DHCP Server
- TFTP BOOT Server
- WINS Server
- FTP Server
- VPN Server
- DNS Server
- DDNS Server
- MySQL Server
- HTTP Apache Server
- Remote Backup Solutions
- Remote control and administration
- Print Queue Server
- Proxy Server

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.

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!

Proxy Detector is a PHP class that can detect HTTP requests via proxy. This class can detect if a visitor uses a proxy server by scanning the headers returned by the user client.
When the user uses a proxy server, most of the proxy servers alter the header. The header is returned to PHP in the array $_SERVER.
Enhancements:
- This is the first release of the class and implementation example.

FSP Proxy provides a proxy server for FSP to HTTP protocol translation.
FSP Proxy is a proxy server for FSP to HTTP/1.0 protocol translation. It also accepts gopher:// URLs as an alias for fsp://. You can set it up as a gopher proxy in your browser, and easily access FSP sites.
This proxy supports HTTP/1.1 on output side and FSP v2 on input side. Subrange byte requests are supported, resume works nicely. Simply FSP v2 over HTTP/1.1. This proxy do not caches anything.
This proxy makes playing with FSP very easy for newcommers, there is no need to learn classic fsp command line interface tools. Everybody who can handle downloads in browser, can now play with FSP sites available through Internet.
Enhancements:
- use getopt from stdio.h instead of getopt.h in fspscan.c
- fspscan now compiles on AIX and other OS without glibc (hoaxter)
- !! fixed fatal bug from b23. Server sends large packets to clients if
- client request has not prefered reply size inside. This confuses
- all old fsp clients.
- common/strdup.c removed
- bsd_src/function.c bcopy -> memmove
- removed STDC_HEADER checks, drop support for pre-ANSI compilers
- started work on alternate SCons based build system
- fspd: use urandom, not random -> avoid hangs on Lin suck 2.6
- build system converted to SCons
- !! fixed directory listing bug in client library introduced in beta23
- improvements to security of FSP clients
- seq. numbers are now randomized
- seed random number generator in fsp clients
- check cmd in received packets
- check pos in received packets