Privoxy 3.0.13 introduces IPv6 support, - improved keep-alive support and a bunch of minor improvements:
Added IPv6 support. Thanks to Petr Pisar who not only provided - the initial patch but also helped a lot with the integration. -
Added client-side keep-alive support. This should also allow - NTLM authentication through Privoxy, but this hasn't been - confirmed yet. -
The connection sharing code is only used if the connection-sharing - option is enabled. -
The max-client-connections option has been added to restrict - the number of client connections below a value enforced by - the operating system. -
Fixed a regression reintroduced in 3.0.12 that could cause - crashes on mingw32 if header date randomization was enabled. -
Compressed content with extra fields couldn't be decompressed - and would get passed to the client unfiltered. This problem - has only be detected through statical analysis with clang as - nobody seems to be using extra fields anyway. -
If the server resets the Connection after sending only the headers - Privoxy forwards what it got to the client. Previously Privoxy - would deliver an error message instead. -
Error messages in case of connection timeouts use the right - HTTP status code. -
If spawning a child to handle a request fails, the client - gets an error message and Privoxy continues to listen for - new requests right away. -
The error messages in case of server-connection timeouts or - prematurely closed server connections are now template-based. -
If zlib support isn't compiled in, Privoxy no longer tries to - filter compressed content unless explicitly asked to do so. -
In case of connections that are denied based on ACL directives, - the memory used for the client IP is no longer leaked. -
Fixed another small memory leak if the client request times out - while waiting for client headers other than the request line. -
The client socket is kept open until the server socket has - been marked as unused. This should increase the chances that - the still-open connection will be reused for the client's next - request to the same destination. Note that this only matters - if connection-sharing is enabled. -
A TODO list has been added to the source tarballs to give potential - volunteers a better idea of what the current goals are. Donations - are still welcome too: http://www.privoxy.org/faq/general.html#DONATE -
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 - 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! -
- On the other hand, other installers don't overwrite existing configuration - files, thinking you will want to do that yourself. -
- standard.action has been merged into - the default.action file. -
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. -
Privoxy 3.0.34 fixes a few minor bugs and comes with a couple of general + improvements and new features.
+Changes in Privoxy 3.0.34 stable:
+Bug fixes:
+Improve the handling of chunk-encoded responses by buffering the data even if filters are disabled and + properly keeping track of where the various chunks are supposed to start and end. Previously Privoxy would + merely check the last bytes received to see if they looked like the last-chunk. This failed to work if the + last-chunk wasn't received in one read and could also result in actual data being misdetected as + last-chunk. Should fix: SF support request #1739. Reported by: withoutname.
+remove_chunked_transfer_coding(): Refuse to de-chunk invalid data Previously the data could get + corrupted even further. Now we simply pass the unmodified data to the client.
+gif_deanimate(): Tolerate multiple image extensions in a row. This allows to deanimate all the gifs on: + https://commons.wikimedia.org/wiki/Category:Animated_smilies Fixes SF bug #795 reported by Celejar.
+OpenSSL generate_host_certificate(): Use X509_get_subject_name() instead of X509_get_issuer_name() to + get the issuer for generated website certificates so there are no warnings in the browser when using an + intermediate CA certificate instead of a self-signed root certificate. Problem reported and patch submitted + by Chakib Benziane.
+can_filter_request_body(): Fix a log message that contained a spurious u.
+handle_established_connection(): Check for pending TLS data from the client before checking if data is + available on the connection. The TLS library may have already consumed all the data from the client + response in which case poll() and select() will not detect that data is available to be read. Sponsored by: + Robert Klemme.
+ssl_send_certificate_error(): Don't crash if there's no certificate information available. This is only + relevant when Privoxy is built with wolfSSL 5.0.0 or later (code not yet published). Earlier wolfSSL + versions or the other TLS backends don't seem to trigger the crash.
+socks5_connect(): Add support for target hosts specified as IPv4 address Previously the IP address was + sent as domain.
+General improvements:
+Add a client-body-tagger action which creates tags based on the content of the request body. Sponsored + by: Robert Klemme.
+When client-body filters are enabled, buffer the whole request before opening a connection to the + server. Makes it less likely that the server connection times out and we don't open a connection if the + buffering fails anyway. Sponsored by: Robert Klemme.
+Add periods to a couple of log messages.
+accept_connection(): Add missing space to a log message.
+Initialize ca-related defaults with strdup_or_die() so errors aren't silently ignored.
+make_path: Use malloc_or_die() in cases where allocation errors were already fatal anyway.
+handle_established_connection(): Improve an error message slightly.
+receive_client_request(): Reject https URLs without CONNECT request.
+Include all requests in the statistics if mutexes are available. Previously in case of reused + connections only the last request got counted. The statistics still aren't perfect but it's an + improvement.
+Add read_socks_reply() and start using it in socks5_connect() to apply the socket timeout more + consistently.
+socks5_connect(): Deal with domain names in the socks reply
+Add a filter for bundeswehr.de that hides the cookie and privacy info banner.
+Action file improvements:
+Disable filter{banners-by-size} for .freiheitsfoo.de/.
+Disable filter{banners-by-size} for freebsdfoundation.org/.
+Disable fast-redirects for consent.youtube.com/.
+Block requests to ups.xplosion.de/.
+Block requests for elsa.memoinsights.com/t.
+Fix a typo in a test.
+Disable fast-redirects for launchpad.net/.
+Unblock .eff.org/.
+Stop unblocking .org/.*(image|banner) which appears to be too generous The example URL + http://www.gnu.org/graphics/gnu-head-banner.png is already unblocked due to .gnu.org being unblocked.
+Unblock adfd.org/.
+Disable filter{banners-by-link} for .eff.org/.
+Block requests to odb.outbrain.com/.
+Disable fast-redirects for .gandi.net/.
+Disable fast-redirects{} for .onion/.*/status/.
+Disable fast-redirects{} for twitter.com/.*/status/.
+Unblock pinkstinks.de/.
+Disable fast-redirects for .hagalil.com/.
+Privoxy-Log-Parser:
+Bump version to 0.9.5.
+Highlight more log messages.
+Highlight the Crunch reason only once. Previously the "crunch reason" could also be highlighted when the + URL contained a matching string. The real crunch reason only occurs once per line, so there's no need to + continue looking for it after it has been found once. While at it, add a comment with an example log + line.
+uagen:
+Bump version to 1.2.4.
+Update BROWSER_VERSION and BROWSER_REVISION to 102.0 to match the User-Agent of the current Firefox + ESR.
+Explicitly document that changing the 'Gecko token' is suspicious.
+Consistently use a lower-case 'c' as copyright symbol.
+Bump copyright.
+Add 'aarch64' as Linux architecture.
+Add OpenBSD architecture 'arm64'.
+Stop using sparc64 as FreeBSD architecture. It hasn't been supported for a while now.
+Build system:
+Makefile: Add a 'dok' target that depends on the 'error' target to show the "You are not using GNU make + or did nor run configure" message.
+configure: Fix --with-msan option. Also (probably) reported by Andrew Savchenko.
+macOS build system:
+Enable HTTPS inspection when building the macOS binary (using OpenSSL as TLS library).
+Documentation:
+Add OpenSSL to the list of libraries that may be licensed under the Apache 2.0 license in which case the + linked Privoxy binary has to be distributed under the GPLv3 or later.
+config: Fix the documented ca-directory default value. Reported by avoidr.
+Rebuild developer-manual and tidy with 'HTML Tidy for FreeBSD version 5.8.0'.
+Update developer manual with new macOS packaging instructions.
+Note that the FreeBSD installation instructions work for ElectroBSD as well.
+Note that FreeBSD/ElectroBSD users can try to install Privoxy as binary package using 'pkg'.
+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 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!
+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.
+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.
+