<title>What's New in this Release</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.23 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.25 User Manual" href="index.html">
<link rel="PREVIOUS" title="Installation" href="installation.html">
<link rel="NEXT" title="Quickstart to Using Privoxy" href=
"quickstart.html">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.23 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.25 User Manual</th>
</tr>
<tr>
<h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this
Release</a></h1>
- <p><span class="APPLICATION">Privoxy 3.0.23</span> stable is a bug-fix
- release, some of the fixed bugs are security issues (CVE requests
- pending):</p>
+ <p><span class="APPLICATION">Privoxy 3.0.25</span> beta introduces
+ client-specific tags and includes a couple of minor improvements. It will be
+ followed by a stable release in the near future.</p>
<ul>
<li>
<ul>
<li>
- <p>Fixed a DoS issue in case of client requests with incorrect
- chunk-encoded body. When compiled with assertions enabled (the
- default) they could previously cause Privoxy to abort(). Reported
- by Matthew Daley.</p>
+ <p>Always use the current toggle state for new requests.
+ Previously new requests on reused connections inherited the
+ toggle state from the previous request even though the toggle
+ state could have changed. Reported by Robert Klemme.</p>
</li>
<li>
- <p>Fixed multiple segmentation faults and memory leaks in the
- pcrs code. This fix also increases the chances that an invalid
- pcrs command is rejected as such. Previously some invalid
- commands would be loaded without error. Note that Privoxy's pcrs
- sources (action and filter files) are considered trustworthy
- input and should not be writable by untrusted third-parties.</p>
+ <p>Fixed two buffer-overflows in the (deprecated) static pcre
+ code. These bugs are not considered security issues as the input
+ is trusted. Found with afl-fuzz and ASAN.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>General improvements:</p>
+
+ <ul>
+ <li>
+ <p>Added support for client-specific tags which allow Privoxy
+ admins to pre-define tags that are set for all requests from
+ clients that previously opted in through the CGI interface. They
+ are useful in multi-user setups where admins may want to allow
+ users to disable certain actions and filters for themselves
+ without affecting others. In single-user setups they are useful
+ to allow more fine-grained toggling. For example to disable
+ request blocking while still crunching cookies, or to disable
+ experimental filters only. This is an experimental feature, the
+ syntax and behaviour may change in future versions. Sponsored by
+ Robert Klemme.</p>
+ </li>
+
+ <li>
+ <p>Dynamic filters and taggers now support a $listen-address
+ variable which contains the address the request came in on. For
+ external filters the variable is called $PRIVOXY_LISTEN_ADDRESS.
+ Original patch contributed by pursievro.</p>
+ </li>
+
+ <li>
+ <p>Add client-header-tagger 'listen-address'.</p>
+ </li>
+
+ <li>
+ <p>Include the listen-address in the log message when logging new
+ requests. Patch contributed by pursievro.</p>
+ </li>
+
+ <li>
+ <p>Turn invalid max-client-connections values into fatal
+ errors.</p>
+ </li>
+
+ <li>
+ <p>The show-status page now shows whether or not dates before
+ 1970 and after 2038 are expected to be handled properly. This is
+ mainly useful for Privoxy-Regression-Test but could also come
+ handy when dealing with time-related support requests.</p>
</li>
<li>
- <p>Fixed an 'invalid read' bug which could at least theoretically
- cause Privoxy to crash. So far, no crashes have been
- observed.</p>
+ <p>On Mac OS X the thread id in log messages are more likely to
+ be unique now.</p>
</li>
<li>
- <p>Compiles with --disable-force again. Reported by Kai
- Raven.</p>
+ <p>When complaining about missing filters, the filter type is
+ logged as well.</p>
</li>
<li>
- <p>Client requests with body that can't be delivered no longer
- cause pipelined requests behind them to be rejected as invalid.
- Reported by Basil Hussain.</p>
+ <p>A couple of harmless coverity warnings were silenced (CID
+ #161202, CID #161203, CID #161211).</p>
</li>
</ul>
</li>
<li>
- <p>General improvements:</p>
+ <p>Action file improvements:</p>
<ul>
<li>
- <p>If a pcrs command is rejected as invalid, Privoxy now logs the
- cause of the problem as text. Previously the pcrs error code was
- logged.</p>
+ <p>Filtering is disabled for Range requests to let download
+ resumption and Windows updates work with the default
+ configuration.</p>
</li>
<li>
- <p>The tests are less likely to cause false positives.</p>
+ <p>Unblock ".ardmediathek.de/". Reported by ThTomate in #932.</p>
</li>
</ul>
</li>
<li>
- <p>Action file improvements:</p>
+ <p>Documentation improvements:</p>
+
+ <ul>
+ <li>
+ <p>Add FAQ entry for crashes caused by memory limits.</p>
+ </li>
+
+ <li>
+ <p>Remove obsolete FAQ entry about a bug in PHP 4.2.3.</p>
+ </li>
+
+ <li>
+ <p>Mention the new mailing lists were appropriate. As the
+ archives have not been migrated, continue to mention the archives
+ at SF in the contacting section for now.</p>
+ </li>
+
+ <li>
+ <p>Note that the templates should be adjusted if Privoxy is
+ running as intercepting proxy without getting all requests.</p>
+ </li>
+
+ <li>
+ <p>A bunch of links were converted to https://.</p>
+ </li>
+
+ <li>
+ <p>Rephrase onion service paragraph to make it more obvious that
+ Tor is involved and that the whole website (and not just the
+ homepage) is available as onion service.</p>
+ </li>
+
+ <li>
+ <p>Streamline the "More information" section on the homepage
+ further by additionally ditching the link to the 'See also'
+ section of the user manual. The section contains mostly links
+ that are directly reachable from the homepage already and the
+ rest is not significant enough to get a link from the
+ homepage.</p>
+ </li>
+
+ <li>
+ <p>Change the add-header{} example to set the DNT header and use
+ a complete section to make copy and pasting more convenient. Add
+ a comment to make it obvious that adding the header is not
+ recommended for obvious reasons. Using the DNT header as example
+ was suggested by Leo Wzukw.</p>
+ </li>
+
+ <li>
+ <p>Streamline the support-and-service template Instead of linking
+ to the various support trackers (whose URLs hopefully change
+ soon), link to the contact section of the user manual to increase
+ the chances that users actually read it.</p>
+ </li>
+
+ <li>
+ <p>Add a FAQ entry for tainted sockets.</p>
+ </li>
+
+ <li>
+ <p>More sections in the documentation have stable URLs now.</p>
+ </li>
+
+ <li>
+ <p>FAQ: Explain why 'ping config.privoxy.org' is not expected to
+ reach a local Privoxy installation.</p>
+ </li>
+
+ <li>
+ <p>Note that donations done through Zwiebelfreunde e.V. currently
+ can't be checked automatically.</p>
+ </li>
+
+ <li>
+ <p>Updated section regarding starting Privoxy under OS X.</p>
+ </li>
+
+ <li>
+ <p>Use dedicated start instructions for FreeBSD and
+ ElectroBSD.</p>
+ </li>
+
+ <li>
+ <p>Removed release instructions for AIX. They haven't been
+ working for years and unsurprisingly nobody seems to care.</p>
+ </li>
+
+ <li>
+ <p>Removed obsolete reference to the solaris-dist target.</p>
+ </li>
+
+ <li>
+ <p>Updated the release instructions for FreeBSD.</p>
+ </li>
+
+ <li>
+ <p>Removed unfinished release instructions for Amiga OS and HP-UX
+ 11.</p>
+ </li>
+
+ <li>
+ <p>Added a pointer to the Cygwin Time Machine for getting the
+ last release of Cygwin version 1.5 to use for building Privoxy on
+ Windows.</p>
+ </li>
+
+ <li>
+ <p>Various typos have been fixed.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Infrastructure improvements:</p>
<ul>
<li>
- <p>'.sify.com/' is no longer blocked. Apparently it is not
- actually a pure tracking site (anymore?). Reported by Andrew on
- ijbswa-users@.</p>
+ <p>The website is no longer hosted at SourceForge and can be
+ reached through https now.</p>
+ </li>
+
+ <li>
+ <p>The mailing lists at SourceForge have been deprecated, you can
+ subscribe to the new ones at: https://lists.privoxy.org/</p>
</li>
<li>
- <p>Unblock banners on .amnesty.de/ which aren't ads.</p>
+ <p>Migrating the remaining services from SourceForge is work in
+ progress (TODO list item #53).</p>
</li>
</ul>
</li>
<li>
- <p>Documentation improvements:</p>
+ <p>Build system improvements:</p>
<ul>
<li>
- <p>The 'Would you like to donate?' section now also contains a
- "Paypal" address.</p>
+ <p>Add configure argument to optimistically redefine FD_SETSIZE
+ with the intent to change the maximum number of client
+ connections Privoxy can handle. Only works with some libcs.
+ Sponsored by Robert Klemme.</p>
+ </li>
+
+ <li>
+ <p>Let the tarball-dist target skip files in ".git".</p>
+ </li>
+
+ <li>
+ <p>Let the tarball-dist target work in cwds other than
+ current.</p>
+ </li>
+
+ <li>
+ <p>Make the 'clean' target faster when run from a git
+ repository.</p>
+ </li>
+
+ <li>
+ <p>Include tools in the generic distribution.</p>
+ </li>
+
+ <li>
+ <p>Let the gen-dist target work in cwds other than current.</p>
+ </li>
+
+ <li>
+ <p>Sort find output that is used for distribution tarballs to get
+ reproducible results.</p>
+ </li>
+
+ <li>
+ <p>Don't add '-src' to the name of the tar ball generated by the
+ gen-dist target. The package isn't a source distribution but a
+ binary package. While at it, use a variable for the name to
+ reduce the chances that the various references get out of sync
+ and fix the gen-upload target which was looking in the wrong
+ directory.</p>
+ </li>
+
+ <li>
+ <p>Add regression-tests.action to the files that are
+ distributed.</p>
+ </li>
+
+ <li>
+ <p>The gen-dist target which was broken since 2002 (r1.92) has
+ been fixed.</p>
+ </li>
+
+ <li>
+ <p>Remove genclspec.sh which has been obsolete since 2009.</p>
+ </li>
+
+ <li>
+ <p>Remove obsolete reference to Redhat spec file.</p>
+ </li>
+
+ <li>
+ <p>Remove the obsolete announce target which has been commented
+ out years ago.</p>
+ </li>
+
+ <li>
+ <p>Let rsync skip files if the checksums match.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Privoxy-Regression-Test:</p>
+
+ <ul>
+ <li>
+ <p>Add a "Default level offset" directive which can be used to
+ change the default level by a given value. This directive affects
+ all tests located after it until the end of the file or a another
+ "Default level offset" directive is reached. The purpose of this
+ directive is to make it more convenient to skip similar tests in
+ a given file without having to remove or disable the tests
+ completely.</p>
+ </li>
+
+ <li>
+ <p>Let test level 17 depend on FEATURE_64_BIT_TIME_T instead of
+ FEATURE_PTHREAD which has no direct connection to the time_t
+ size.</p>
</li>
<li>
- <p>The list of supported operating systems has been updated.</p>
+ <p>Fix indentation in perldoc examples.</p>
</li>
<li>
- <p>The existence of the SF support and feature trackers has been
- deemphasized because they have been broken for months. Most of
- the time the mailing lists still work.</p>
+ <p>Don't overlook directives in the first line of the action
+ file.</p>
</li>
<li>
- <p>The claim that default.action updates are sometimes released
- on their own has been removed. It hasn't happened in years.</p>
+ <p>Bump version to 0.7.</p>
</li>
<li>
- <p>Explicitly mention that Tor's port may deviate from the
- default when using a bundle. Requested by Andrew on
- ijbswa-users@.</p>
+ <p>Fix detection of the Privoxy version now that https:// is used
+ for the website.</p>
</li>
</ul>
</li>
projects / privoxy.git / blobdiff