| Privoxy 3.0.25 User Manual | +Privoxy 3.0.32 User Manual | ||||
|---|---|---|---|---|---|
| Prev | - +Prev | - - | Next | +Next | |
Privoxy 3.0.25 beta introduces - client-specific tags and includes a couple of minor improvements. It will be - followed by a stable release in the near future.
- +Privoxy 3.0.31 fixes two security issues that were discovered while preparing + the 3.0.30 release. The issues also affect earlier Privoxy releases.
+Changes in Privoxy 3.0.31 stable:
+Security/Reliability:
+Prevent an assertion from getting triggered by a crafted CGI request. Commit 5bba5b89193fa. + OVE-20210130-0001. Reported by: Joshua Rogers (Opera)
+Fixed a memory leak when decompression fails "unexpectedly". Commit f431d61740cc0. + OVE-20210128-0001.
+Bug fixes:
+Fixed detection of insufficient data for decompression. Previously Privoxy could try to decompress a + partly uninitialized buffer.
+Changes in Privoxy 3.0.30 stable:
Bug fixes:
-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.
+Check the actual URL for redirects when https inspecting requests. Previously Privoxy would only check + the path which resulted in rewrite results being rejected as invalid URLs. Reported by withoutname in + #1736.
+Let the hide-referrer code tolerate Referer headers with https:// URLs. Previously they would always be + treated like a changed host.
+Use the https headers if the show-request handler is reached through https://. Previously Privoxy would + use the http headers which may be empty on a reused connection.
+Make CGI_PREFIX protocol-relative when building with FEATURE_HTTPS_INSPECTION. This unbreaks (at least) + https://config.privoxy.org/client-tags whose buttons would previously use a http:// URL resulting in + browser warnings.
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.
+Support using https-inspection and client-header-order at the same time. Previously Privoxy would crash. + Reported by: Kai Raven
+Properly reject rewrites from http to https as they currently aren't supported. Previously Privoxy would + wait for the client to establish an encrypted connection which obviously would not happen.
+When https inspection is enabled and Privoxy has been compiled with FEATURE_GRACEFUL_TERMINATION (not + recommended for production builds), the TLS backend resources are free'd later on and only if no active + connections are left. Prevents crashes when exiting "gracefully" at the wrong time.
+Let the uninstall target remove the config file even if DESTDIR is set and properly announce the + deletion of the configuration files.
General improvements:
-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.
+Allow to rewrite the request destination for https-inspected requests behind the client's back. The + documentation already sort of claimed that it was supported by not especially mentioning that it didn't + work for https-inspected requests. Fixes SF bug #923 reported by withoutname.
+Add support for filtering client request bodies by using CLIENT-BODY-FILTER filters which can be enabled + with the client-body-filter action. Patch submitted by Maxim Antonov. Sponsored by: Robert Klemme
+Add the new action suppress-tag{} which can be used to prevent a tagger from adding a tag. Patch + submitted by Maxim Antonov. Sponsored by: Robert Klemme
+Gracefully handle existing website keys without matching certificates. This can happen if Privoxy was + previously running with an invalid TLS configuration that didn't allow it to create a certificate.
+Recycle debug bit 4 for Tagging-related messages.
+Improve the message shown when the client-tags CGI page is requested with no tags configured.
+Shorten the 'donate' and 'participate' links used by templates using redirects. Currently the redirects + lead to the FAQ entries but in the future we may want to relocate the content and using redirects makes + this more convenient.
+Log an error when a PCRE-HOST-PATTERN is used with FEATURE_PCRE_HOST_PATTERNS disabled. Don't treat this + a fatal error so the regression tests can be used with and without FEATURE_PCRE_HOST_PATTERNS.
+The code compiles with older C compilers again.
+The chdir() return code is checked to fix a compiler warning.
+The packages feed has been removed from the source tarball. It's usually out of date when the source + tarball is generated for the release.
+Fixed harmless compiler warnings from GCC9 with -D_FORTIFY_SOURCE=2.
+windows: Remove obsolete '$(DEST)/doc/images' target.
+windows: Install the images referenced in the user manual.
+Remove obsolete 'gnu_regex.@OBJEXT@' target.
+When installing from the GNUMAkefile, don't create an 'images' directory which is no longer used. The + images were relocated to the user-manual directory years ago.
+Add new FEATURES to the show-status page and resort list.
+Remove unused variable in the OpenSSL-specific code.
+Update bug tracker URL in cgi_error_unknown().
+Saved a couple of memory allocations when sorting client headers.
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.
+Improved a couple of error messages.
Add client-header-tagger 'listen-address'.
+Saved memory allocations when using OpenSSL and checking if a key already exists.
Include the listen-address in the log message when logging new - requests. Patch contributed by pursievro.
+The configure script will bail out if OpenSSL and mbedTLS are enabled at the same time.
Turn invalid max-client-connections values into fatal - errors.
+Log a message right before exiting gracefully.
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.
+A couple of structures have been rearranged to require slightly less memory.
On Mac OS X the thread id in log messages are more likely to - be unique now.
+When https inspection is enabled and the certificate is invalid the error message is now sent with + status code 403 instead of 200.
When complaining about missing filters, the filter type is - logged as well.
+The Slackware rc script template has been renamed to slackware/rc.privoxy.in to silence complaints when + building Debian packages.
A couple of harmless coverity warnings were silenced (CID - #161202, CID #161203, CID #161211).
+When building with MbedTLS support, mbedtls_md5_ret() is used instead of mbedtls_md5() which is + deprecated and causes a warning on Debian GNU/Linux.
Action file improvements:
-Filtering is disabled for Range requests to let download - resumption and Windows updates work with the default - configuration.
+Block requests to eu-tlp03.kameleoon.com/.
+Unblock metrics.sr.ht/.
+Disable fast-redirects for .fsf.org/.
+Disable fast-redirects for .gravater.com/.
+Disable fast-redirects for .ksta.de/.
+Block requests to tag.crsspxl.com/.
+Block requests to analytics.slashdotmedia.com/.
+Block requests to ml314.com/.
+Block requests to .adroll.com/.
+Block requests to fastlane.rubiconproject.com/.
+Block requests to api.theadex.com/.
+Block requests to ih.adscale.de/.
+Block requests to .s400.meetrics.net/.
+Block requests for pp.lp4.io/.
Unblock ".ardmediathek.de/". Reported by ThTomate in #932.
+Block requests for trc-events.taboola.com/.
Documentation improvements:
- +Filter file improvements:
Add FAQ entry for crashes caused by memory limits.
+A allow-autocompletion filter has been added which changes autocomplete="off" to "on" on input fields to + allow autocompletion. Requested by Jamie Zawinski in #370. Filter based on a submission by Aaron + Linville.
+Added an imdb filter.
+Added a sourceforge filter that reduces the amount of ads for proprietary software.
Remove obsolete FAQ entry about a bug in PHP 4.2.3.
+Added a github filter that removes the annoying "Sign-Up" banner and the Cookie disclaimer.
+Removed a duplicated pcrs command from the js-annoyances filter.
+The crude-parental filter now provides a short reason when blocking, inserts a link to Privoxy's + webinterface and adds a new line at the end of the generated page.
+Privoxy-Log-Parser:
+Highlight a few more messages.
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.
+Add a handler for tagging messages.
Note that the templates should be adjusted if Privoxy is - running as intercepting proxy without getting all requests.
+Properly deal with 'Certificate error' crunches Previously the error description was highlighted as + 'host'.
A bunch of links were converted to https://.
+Log truncated LOG_LEVEL_CLF messages more gracefully and note that the statistics will be imprecise.
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.
+Fixed perldoc typo.
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.
+Bump version to 0.9.2.
Privoxy-Regression-Test:
+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.
+Use http://127.0.0.1:8118/ as default Privoxy address unless http_proxy is set through the + environment.
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.
+Add a --privoxy-cgi-prefix option that specifies the prefix to use when building URLs that are supposed + to reach Privoxy's CGI interface. If it's not set, http://p.p/ is used, which is supposed to work with the + default Privoxy configuration. If Privoxy has been built with FEATURE_HTTPS_INSPECTION enabled, and if + https inspection is activated with the +https-inspection action, this option can be used with + "https://p.p/" provided the system running Privoxy-Regression-Test has been configured to trust the + certificate used by Privoxy. Note that there are currently two tests in the official + regression-tests.action file that are expected to fail when using "https://p.p/" as privoxy-cgi-prefix.
Add a FAQ entry for tainted sockets.
+Skip the connection-established response in get_status_code() when looking for the status code with a + CGI prefix that starts with https://. We care about the status code sent by the impersonated web + server.
More sections in the documentation have stable URLs now.
+Use --proxy-header when using a CGI prefix with https:// and a "Host:" header.
FAQ: Explain why 'ping config.privoxy.org' is not expected to - reach a local Privoxy installation.
+Allow '|' in tokens and values to allow tag patterns like + "TAG:^(application|text)/(x-)?javascript$".
Note that donations done through Zwiebelfreunde e.V. currently - can't be checked automatically.
+When get_cgi_page_or_else() fails, include the URL of the requested page in the log message.
Updated section regarding starting Privoxy under OS X.
+Added a --check-bad-ssl option that can be used to verify that Privoxy detects certificate problems when + accessing the test sites from badssl.com.
Use dedicated start instructions for FreeBSD and - ElectroBSD.
+Bumped version to 0.7.2
uagen:
+Removed release instructions for AIX. They haven't been - working for years and unsurprisingly nobody seems to care.
+Update example output.
Removed obsolete reference to the solaris-dist target.
+Recommend the use of the https-inspection action in the documentation.
Updated the release instructions for FreeBSD.
+Upgrade a couple of URLs to https://.
Removed unfinished release instructions for Amiga OS and HP-UX - 11.
+Add ElectroBSD to the list of operating systems.
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.
+Bumped generated Firefox version to 78 (ESR).
Various typos have been fixed.
+Bumped version to 1.2.2.
Infrastructure improvements:
- +User documentation:
The website is no longer hosted at SourceForge and can be - reached through https now.
+Remove reference to 'How to Report Bugs Effectively'. It was only rendered as text without URL in the + README anyway and there's no indication that users read it ...
+Let the dok-readme target fix the location embedded into the README file. This used to be done by CVS + but since the git migration it has to be done through other means.
+Remove 'experimental' warning for client-specific-tag-related directives. They seem to work reliably and + there is no obvious reason why we would change the syntax in the near future.
The mailing lists at SourceForge have been deprecated, you can - subscribe to the new ones at: https://lists.privoxy.org/
+Describe how to check if Privoxy has been built with FEATURE_HTTPS_INSPECTION.
Migrating the remaining services from SourceForge is work in - progress (TODO list item #53).
+Add a link to the trusted-cas-file documentation that explains how the user can create the file + herself.
+Don't explicitly mention the license for the code coming from 'Anonymous Coders' and Junkbusters. It's + obviously licensed under the GNU GPL like the rest of Privoxy or we wouldn't be allowed to distribute + it.
+Update the +hide-user-agent example with uagen output.
+Slightly improve the wording of the ca-key-file documentation.
+Explicitly mention Windows 10 as supported so search engines and users looking for it can find it.
+Import a bunch of contributors from the ChangeLog.
+Remove obsolete doc/gpl.html.
+Upgrade a couple of links to https://.
+Don't prefer the SourceForge patch tracker over the privoxy-devel mailing list. While at it, link to the + SourceForge patch tracker.
+Mention http-inspection in the 'my browser warns me about unauthenticated content' FAQ entry.
+Simplify the 'Is there is a license or fee?' FAQ entry.
+Add another +redirect{} example.
+Explicitly mention that interested sponsors should include the link target in their first mail.
+Clarify that only Privoxy team members can object to new sponsors and link to the list of current team + members.
+Note that sponsor URLs may not contain keyword spam.
+Garbage collect doc/webserver/images which isn't referenced anymore.
+Update the method to reach the proxy settings in Firefox.
+Update proxy_setup.jpg description to refer to Firefox.
+Regenerate proxy_setup.jpg with a more recent Firefox (78.0).
+Regenerate files-in-use.jpg without obsolete standard.action with modern colors and a slightly better + quality.
+Update URL to the actionsfile tracker.
+Update a support request URL.
+Rephrase the 'Can Privoxy run as service' FAQ entry and remove an obsolete paragraph.
+Let the 'Where can I get updated Actions Files?' entry link to the gitweb version of + default.action.master.
+Update a link to the default.action file.
+Update URLs for trackers and mailing lists.
+Replace CVS reference with git.
+Mention regression-tests.action in the config file.
+Explicitly mention in the config file that access to the CA key should be limited to Privoxy.
+List more client-specific-tag examples for inspiration.
+Add additional headers to the client-header-order example.
+Note that actions aren't updated after rewrites.
+Explicitly mention that upgrading from http to https with a client-header filter is not supported
+Note that protocol and host have to be added when rewriting the destination host for https-inspected + requests.
+Explicitly mention that the CA key is used to sign certificates.
+Put openssl command in 'command' tags.
+The man page has been moved from section 1 to man section 8.
Build system improvements:
- +Developer manual:
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.
+Flesh out the build instructions for Debian.
+Remove the packaging instructions for RPM-based systems. They don't work and we don't release RPM + packages anymore anyway.
+Remove the packaging instructions for Solaris. They don't work and we don't release Solaris packages + anymore anyway.
+Update the suggested subject for the announce mails.
+Update upload instructions. ftp://upload.sourceforge.net is no longer functional.
+Remove a couple of package-dependent upload instructions that don't actually work.
+Remove 'cd current' that no longer works.
+Add regression-tests.action to the list of files that should be installed.
+Stop claiming that there are text versions of the manuals. We stopped building them in 2008 + (9ed36a3c5e6f12).
+Note that the 'webserver' target creates the link needed for the user-manual.
Let the tarball-dist target skip files in ".git".
+Suggest to use the master branch as reference when creating the ChangeLog so the steps work when the + current branch differs from master which is likely as the developer manual suggests to use a local branch + for development.
Let the tarball-dist target work in cwds other than - current.
+Add the -s flag to the suggested 'git tag' command. We prefer signed tags.
Make the 'clean' target faster when run from a git - repository.
+Mention that merges into 'master' should be avoided.
Include tools in the generic distribution.
+Add git commands that should result in a merge-free history.
Let the gen-dist target work in cwds other than current.
+Mention Privoxy-Regression-Test.
Sort find output that is used for distribution tarballs to get - reproducible results.
+Add a section id to reduce link churn.
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.
+Recommend the dok-tidy target when building docs for the webserver.
Add regression-tests.action to the files that are - distributed.
+Add another plug for the privoxy-devel mailing list.
The gen-dist target which was broken since 2002 (r1.92) has - been fixed.
+Let the intro link the copyright section in the user manual instead of giving an incomplete summary of + the license status.
Remove genclspec.sh which has been obsolete since 2009.
+Clarify that the webserver target uploads to the SourceForge webserver.
Remove obsolete reference to Redhat spec file.
+Mark the documentation for the Mac OS X installers as out of date and change the SCM name back to + CVS.
Remove the obsolete announce target which has been commented - out years ago.
+Fix the location of the installer modules for Mac OS X. They are not actually available through git + (yet).
Let rsync skip files if the checksums match.
+Don't speak of Privoxy version 3 in the past tense.
+Update the list of programs required for the release process.
+Update description of the webserver target which uses ssh, not scp.
+Remove obsolete reference to config.new.
Privoxy-Regression-Test:
- +Tests:
+Add another hide-referrer{conditional-block} test.
+Add another hide-referrer{conditional-forge} test.
+Fix a hide-referrer{conditional-forge} test that expected an acceptable header to be forged.
+Fix a hide-referrer{conditional-block} test that expected an acceptable Referer to be removed.
+Explain why the "Set Header = Host: whatever.example.org" test is expected to fail when using a CGI + prefix that starts with "https://".
+Explain why a connection-sharing test is known to fail when using "https://p.p/" as CGI prefix.
+Add a link to Privoxy-Regression-Test to regression-tests.action in case it isn't packaged.
+Add regression tests for pcre host patterns.
+Fixed a regression test that is executed when FEATURE_GRACEFUL_TERMINATION is enabled.
+Privoxy infrastructure:
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.
+Import a Privoxy logo for the website.
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.
+Update Tor onion service to HiddenServiceVersion 3.
Fix indentation in perldoc examples.
+Display the "model" photos in a single row and remove placeholder images.
Don't overlook directives in the first line of the action - file.
+Regenerate homepage with updated sponsor list.
Bump version to 0.7.
+Use the '/sponsor' redirect for the link to the sponsor page.
Fix detection of the Privoxy version now that https:// is used - for the website.
+Git commit messages are sent to the Privoxy-commits mailing list.
A quick list of things to be aware of before upgrading from earlier - versions of Privoxy:
- +A quick list of things to be aware of before upgrading from earlier versions of Privoxy:
The recommended way to upgrade Privoxy is to backup your old configuration - files, install the new ones, verify that Privoxy is working correctly and finally merge - back your changes using diff and - maybe patch.
- -There are a number of new features in each Privoxy release and most of them have to be - explicitly enabled in the configuration files. Old configuration - files obviously don't do that and due to syntax changes using old - configuration files with a new The recommended way to upgrade Privoxy is to backup your old + configuration files, install the new ones, verify that Privoxy is working + correctly and finally merge back your changes using diff and maybe + patch.
+There are a number of new features in each Privoxy release and most of + them have to be explicitly enabled in the configuration files. Old configuration files obviously don't do + that and due to syntax changes using old configuration files with a new Privoxy isn't always possible anyway.
Note that some installers remove earlier versions completely, - including configuration files, therefore you should really save any - important configuration files!
+Note that some installers remove earlier versions completely, including configuration files, therefore you + should really save any important configuration files!
On the other hand, other installers don't overwrite existing - configuration files, thinking you will want to do that - yourself.
+On the other hand, other installers don't overwrite existing configuration files, thinking you will want + to do that yourself.
In the default configuration only fatal errors are logged now. - You can change that in the debug - section of the configuration file. You may also want to enable - more verbose logging until you verified that the new Privoxy version is working as expected.
+In the default configuration only fatal errors are logged now. You can change that in the debug section of the configuration file. You may also want to enable more verbose + logging until you verified that the new Privoxy version is working as + expected.
Three other config file settings are now off by default: - enable-remote-toggle, - enable-remote-http-toggle, - and enable-edit-actions. If you - use or want these, you will need to explicitly enable them, and be - aware of the security issues involved.
+Three other config file settings are now off by default: enable-remote-toggle, enable-remote-http-toggle, and enable-edit-actions. If you use or want these, you will need to + explicitly enable them, and be aware of the security issues involved.