Michael Adam 4292fe7795 Fix a segfault in insert_acl and checks against string-type acls
The "address" member of struct acl_s is a union of a char *
and the numeric ip. So freeing the string after appending it to the
vector list is bad in two respects:

1. If the acl type was numeric, then this could (and would)
   lead to a segfault due to the numeric IP data interpreted
   as pointer to the string to be freed.

2. If the acl type was string, then the acl inserted into the
   list contained a reference to this address string that
   was freed. So in the worst case dereferencing this freed
   string could segfault, or at least this could lead to
   unexpectedly failing acl checks.

Michael
2009-11-10 00:37:57 +01:00
2009-10-11 13:21:13 +02:00
2009-09-27 08:09:24 +05:30
2004-08-10 21:24:24 +00:00
2009-11-09 01:14:03 +05:30
2009-08-04 04:21:46 +05:30
2009-09-28 19:08:54 +05:30
2009-09-27 19:09:51 +05:30
2009-10-13 23:52:02 +02:00

Tinyproxy
=========

Tinyproxy is a small, efficient HTTP/SSL proxy daemon released under the
GNU General Public License.  Tinyproxy is very useful in a small network
setting, where a larger proxy would either be too resource intensive, or
a security risk.  One of the key features of Tinyproxy is the buffering
connection concept.  In effect, Tinyproxy will buffer a high speed
response from a server, and then relay it to a client at the highest
speed the client will accept.  This feature greatly reduces the problems
with sluggishness on the Internet.  If you are sharing an Internet
connection with a small network, and you only want to allow HTTP
requests to be allowed, then Tinyproxy is a great tool for the network
administrator.

For more info, please visit:

	https://www.banu.com/tinyproxy/


Installation
------------

To install this package under a UNIX derivative, read the INSTALL file.
Tinyproxy uses a standard GNU `configure` script. Basically you should
be able to do:

----
./configure
make
make install
----

in the top level directory to compile and install Tinyproxy. There are
additional command line arguments you can supply to `configure`. They
include:

	--enable-debug		If you would like to turn on full
				debugging support
	--enable-xtinyproxy	Compile in support for the XTinyproxy
				header, which is sent to any web
				server in your domain.
	--enable-filter		Allows Tinyproxy to filter out certain
				domains and URLs.
	--enable-upstream	Enable support for proxying connections
				through another proxy server.
	--enable-transparent-proxy
				Allow Tinyproxy to be used as a
				transparent proxy daemon
	--enable-static		Compile a static version of Tinyproxy

        --with-stathost=HOST	Set the default name of the stats host


Support
-------

If you are having problems with Tinyproxy, please submit a bug report
using Tinyproxy as the component at:

	https://www.banu.com/bugzilla/

You may also wish to subscribe to the Tinyproxy mailing lists. To do so
please visit:

	https://www.banu.com/mailman/listinfo/tinyproxy-announce-list
	https://www.banu.com/mailman/listinfo/tinyproxy-users-list
	https://www.banu.com/mailman/listinfo/tinyproxy-developers-list

for more information on how to subscribe and post messages to the lists.


Contributing
------------

If you would like to contribute a feature, or a bug fix to the Tinyproxy
source, please send a patch (preferably as a unified diff. i.e. `diff
-u` against the "master" branch of the Tinyproxy source code git
repository to tinyproxy-developers-list.  Please include a description
of what your patch does.

Tinyproxy's git repository is git://www.banu.com/tinyproxy.git. The
following command creates a local copy:

----
git clone git://www.banu.com/tinyproxy.git
----

The easiest and preferred way to create a patch for submission is to
check in your changes locally and use `git format-patch` to generate a
mbox-style commit file that contains the diff along with the commit
message and author information.  Such a format-patch file can be
integrated into the upstream repository, automatically keeping the
commit message and author information.

You can also meet developers and discuss development issues and patches
in the #tinyproxy IRC channel on Freenode (irc.freenode.net).
Description
No description provided
Readme 2.2 MiB
Languages
C 88.8%
Perl 3.9%
M4 2.7%
Shell 2.7%
Makefile 1%
Other 0.9%