1 Announcing Privoxy 3.0.25 beta
2 --------------------------------------------------------------------
4 Privoxy 3.0.25 beta introduces client-based tags and includes a
5 couple of minor improvements. It will be followed by a stable
6 release in the near future.
7 --------------------------------------------------------------------
9 --------------------------------------------------------------------
11 - Always use the current toggle state for new requests.
12 Previously new requests on reused connections inherited
13 the toggle state from the previous request even though
14 the toggle state could have changed.
15 Reported by Robert Klemme.
16 - Fixed two buffer-overflows in the (deprecated) static
17 pcre code. These bugs are not considered security issues
18 as the input is trusted.
19 Found with afl-fuzz and ASAN.
21 - General improvements:
22 - Added support for client-specific tags which allow Privoxy
23 admins to pre-define tags that are set for all requests from
24 clients that previously opted in through the CGI interface.
25 They are useful in multi-user setups where admins may
26 want to allow users to disable certain actions and filters
27 for themselves without affecting others.
28 In single-user setups they are useful to allow more fine-grained
29 toggling. For example to disable request blocking while still
30 crunching cookies, or to disable experimental filters only.
31 This is an experimental feature, the syntax and behaviour may
32 change in future versions.
33 Sponsored by Robert Klemme.
34 - Dynamic filters and taggers now support a $listen-address variable
35 which contains the address the request came in on.
36 For external filters the variable is called $PRIVOXY_LISTEN_ADDRESS.
37 Original patch contributed by pursievro.
38 - Add client-header-tagger 'listen-address'.
39 - Include the listen-address in the log message when logging new requests.
40 Patch contributed by pursievro.
41 - Turn invalid max-client-connections values into fatal errors.
42 - The show-status page now shows whether or not dates before 1970
43 and after 2038 are expected to be handled properly.
44 This is mainly useful for Privoxy-Regression-Test but could
45 also come handy when dealing with time-related support requests.
46 - On Mac OS X the thread id in log messages are more likely to
48 - When complaining about missing filters, the filter type is logged
50 - A couple of harmless coverity warnings were silenced
51 (CID #161202, CID #161203, CID #161211).
53 - Action file improvements:
54 - Filtering is disabled for Range requests to let download resumption
55 and Windows updates work with the default configuration.
56 - Unblock ".ardmediathek.de/".
57 Reported by ThTomate in #932.
59 - Documentation improvements:
60 - Add FAQ entry for crashes caused by memory limits.
61 - Remove obsolete FAQ entry about a bug in PHP 4.2.3.
62 - Mention the new mailing lists were appropriate.
63 As the archives have not been migrated, continue to
64 mention the archives at SF in the contacting section
66 - Note that the templates should be adjusted if Privoxy is
67 running as intercepting proxy without getting all requests.
68 - A bunch of links were converted to https://.
69 - Rephrase onion service paragraph to make it more obvious
70 that Tor is involved and that the whole website (and not
71 just the homepage) is available as onion service.
72 - Streamline the "More information" section on the homepage further
73 by additionally ditching the link to the 'See also' section
74 of the user manual. The section contains mostly links that are
75 directly reachable from the homepage already and the rest is
76 not significant enough to get a link from the homepage.
77 - Change the add-header{} example to set the DNT header
78 and use a complete section to make copy and pasting
80 Add a comment to make it obvious that adding the
81 header is not recommended for obvious reasons.
82 Using the DNT header as example was suggested by
84 - Streamline the support-and-service template
85 Instead of linking to the various support trackers
86 (whose URLs hopefully change soon), link to the
87 contact section of the user manual to increase the
88 chances that users actually read it.
89 - Add a FAQ entry for tainted sockets.
90 - More sections in the documentation have stable URLs now.
91 - FAQ: Explain why 'ping config.privoxy.org' is not expected
92 to reach a local Privoxy installation.
93 - Note that donations done through Zwiebelfreunde e.V. currently
94 can't be checked automatically.
95 - Updated section regarding starting Privoxy under OS X.
96 - Use dedicated start instructions for FreeBSD and ElectroBSD.
97 - Removed release instructions for AIX. They haven't been working
98 for years and unsurprisingly nobody seems to care.
99 - Removed obsolete reference to the solaris-dist target.
100 - Updated the release instructions for FreeBSD.
101 - Removed unfinished release instructions for Amiga OS and HP-UX 11.
102 - Added a pointer to the Cygwin Time Machine for getting the last release of
103 Cygwin version 1.5 to use for building Privoxy on Windows.
104 - Various typos have been fixed.
106 - Infrastructure improvements:
107 - The website is no longer hosted at SourceForge and
108 can be reached through https now.
109 - The mailing lists at SourceForge have been deprecated,
110 you can subscribe to the new ones at: https://lists.privoxy.org/
111 - Migrating the remaining services from SourceForge is
112 work in progress (TODO list item #53).
114 - Build system improvements:
115 - Add configure argument to optimistically redefine FD_SETSIZE
116 with the intent to change the maximum number of client
117 connections Privoxy can handle. Only works with some libcs.
118 Sponsored by Robert Klemme.
119 - Let the tarball-dist target skip files in ".git".
120 - Let the tarball-dist target work in cwds other than current.
121 - Make the 'clean' target faster when run from a git repository.
122 - Include tools in the generic distribution.
123 - Let the gen-dist target work in cwds other than current.
124 - Sort find output that is used for distribution tarballs
125 to get reproducible results.
126 - Don't add '-src' to the name of the tar ball generated by the
127 gen-dist target. The package isn't a source distribution but a
129 While at it, use a variable for the name to reduce the chances
130 that the various references get out of sync and fix the gen-upload
131 target which was looking in the wrong directory.
132 - Add regression-tests.action to the files that are distributed.
133 - The gen-dist target which was broken since 2002 (r1.92) has been fixed.
134 - Remove genclspec.sh which has been obsolete since 2009.
135 - Remove obsolete reference to Redhat spec file.
136 - Remove the obsolete announce target which has been commented out years ago.
137 - Let rsync skip files if the checksums match.
139 - Privoxy-Regression-Test:
140 - Add a "Default level offset" directive which can be used to
141 change the default level by a given value.
142 This directive affects all tests located after it until the end
143 of the file or a another "Default level offset" directive is reached.
144 The purpose of this directive is to make it more convenient to skip
145 similar tests in a given file without having to remove or disable
146 the tests completely.
147 - Let test level 17 depend on FEATURE_64_BIT_TIME_T
148 instead of FEATURE_PTHREAD which has no direct connection
150 - Fix indentation in perldoc examples.
151 - Don't overlook directives in the first line of the action file.
152 - Bump version to 0.7.
153 - Fix detection of the Privoxy version now that https://
154 is used for the website.
156 -----------------------------------------------------------------
158 -----------------------------------------------------------------
160 Privoxy is a non-caching web proxy with advanced filtering capabilities for
161 enhancing privacy, modifying web page data and HTTP headers, controlling
162 access, and removing ads and other obnoxious Internet junk. Privoxy has a
163 flexible configuration and can be customized to suit individual needs and
164 tastes. It has application for both stand-alone systems and multi-user
167 Privoxy is Free Software and licensed under the GNU GPLv2.
169 Our TODO list is rather long. Helping hands and donations are welcome:
171 * https://www.privoxy.org/faq/general.html#PARTICIPATE
173 * https://www.privoxy.org/faq/general.html#DONATE
175 At present, Privoxy is known to run on Windows 95 and later versions
176 (98, ME, 2000, XP, Vista, Windows 7 etc.), GNU/Linux (RedHat, SuSE,
177 Debian, Fedora, Gentoo, Slackware and others), Mac OS X (10.4 and
178 upwards on PPC and Intel processors), OS/2, Haiku, DragonFly, ElectroBSD,
179 FreeBSD, NetBSD, OpenBSD, Solaris, and various other flavors of Unix.
181 In addition to the core features of ad blocking and cookie management,
182 Privoxy provides many supplemental features, that give the end-user
183 more control, more privacy and more freedom:
185 * Supports "Connection: keep-alive". Outgoing connections can be kept
186 alive independently from the client. Currently not available on all
189 * Supports IPv6, provided the operating system does so too,
190 and the configure script detects it.
192 * Supports tagging which allows to change the behaviour based on client
195 * Can be run as an "intercepting" proxy, which obviates the need to
196 configure browsers individually.
198 * Sophisticated actions and filters for manipulating both server and
201 * Can be chained with other proxies.
203 * Integrated browser based configuration and control utility at
204 http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based
205 tracing of rule and filter effects. Remote toggling.
207 * Web page filtering (text replacements, removes banners based on size,
208 invisible "web-bugs" and HTML annoyances, etc.)
210 * Modularized configuration that allows for standard settings and user
211 settings to reside in separate files, so that installing updated actions
212 files won't overwrite individual user settings.
214 * Support for Perl Compatible Regular Expressions in the configuration
215 files, and a more sophisticated and flexible configuration syntax.
219 * Bypass many click-tracking scripts (avoids script redirection).
221 * User-customizable HTML templates for most proxy-generated pages (e.g.
224 * Auto-detection and re-reading of config file changes.
226 * Most features are controllable on a per-site or per-location basis.
230 https://www.privoxy.org/
232 - Privoxy Developers <privoxy-devel@lists.privoxy.org>
projects / privoxy.git / blob