Privoxy 4.1.0 fixes a few minor bugs and brings ZStandard-decompression$$$support and a couple of general improvements.$$$--------------------------------------------------------------------$$$ChangeLog for Privoxy 4.1.0$$$--------------------------------------------------------------------$$$- General improvements:$$$ - Add Zstandard-decompression support.$$$ - compile_pattern(): Use pcre2_get_error_message() to provide better error messages.$$$ - wolfssl: Use wolfTLS_client_method() instead of wolfSSLv23_method()$$$ when creating the connection to the server. Allows to connect to$$$ https://media.ccc.de/ and https://traxxas.com/ while wolfSSLv23_method()$$$ currently doesnt (wolfSSL 5.8.4). Unfortunately this does not allow to$$$ connect to https://www.fsf.org/ while wolfSSLv23_method() does.$$$ Reported upstream in https://github.com/wolfSSL/wolfssl/issues/7735.$$$ curl is using wolfTLS_client_method() with recent wolfSSL versions$$$ as well so this seems to be the way to go.$$$ - wolfssl: Warn if HAVE_SECURE_RENEGOTIATION is unavailable$$$ and dont suggest to use HAVE_RENEGOTIATION_INDICATION instead.$$$ - show-status template: Add links for external (de)compression libraries.$$$ - If the server sends multiple Connection headers; only parse and$$$ forward the first one.$$$ - create_hexadecimal_hash_of_host(): Use snprintf() instead of sprint()$$$ Silences a warning on OpenBSD.$$$ - Also log the listening address and port the request came in on.$$$ - Added periods to a couple of log messages.$$$ - Removed support for pcre1.$$$ - configure.in: Removed obsolete warning if OpenSSL is detected.$$$ Recent OpenSSL versions are licensed under the Apache 2 license so$$$ the special exception from section 3 of the GPLv2 isnt needed$$$ and a Privoxy binary linked to OpenSSL can be distributed under the$$$ GPLv3 or later.$$$ - init_domain_components(): Assert that the http->dbuffer and http->dvec$$$ are NULL to detect memory leaks earlier.$$$$$$- Bug fixes:$$$ - openssl: Dont call SSL_set_tlsext_host_name() if the host is an IP address$$$ With LibreSSl the call simply fails and with OpenSSL the call$$$ succeeds but results in an syntactically incorrect ClientHello$$$ a server may object to. While at it; add the host name to the error message.$$$ - Dont forward connection options Privoxy doesnt understand.$$$ - Look for the keep-alive keyword more carefully in Connection headers.$$$ Previously connections were not kept alive if the Connection header$$$ contained additional keywords like Upgrade.$$$ - If the MS IIS5 hack fails; only send the error response if were buffering content$$$ Previously the error response was also sent if the client already$$$ received the HTTP headers from the server.$$$ - Fix compilation when configured with --disable-ipv6-support.$$$ Submitted by Luca Broglio.$$$ - Fixed detection and use of pcre2.h from a subdirectory.$$$ SF bug #946. Patch submitted by Jakub Kulik.$$$ - Properly handle IPv6 addresses in the Host header.$$$ Reported by Joshua Rogers.$$$ - socks4_connect(): Fix the dstsize passed to strlcpy() in case of socks4a.$$$ Previously Privoxy would substract sizeof(struct socks_op) twice$$$ as its already part of csiz. While this was wrong it didnt$$$ cause any actual problems as the buffer size is so large that$$$ it didnt matter. Reported by Joshua Rogers.$$$ - error_response(): Prevent a theoretical memory leak. Reported by Joshua Rogers.$$$ - log_error(): Fix a segmentation fault when logging %E on a platform that$$$ isnt Windows and doesnt have strerror(). Reported by Joshua Rogers.$$$ - accept_connection(): Fix memory and socket leak if the server name and$$$ port number ASCII decimal representation dont fit. This is not expected$$$ to happen. Reported by Joshua Rogers.$$$ - parse_http_url(): Fail if no host is found when we expected one.$$$ This can happen in case of invalid requests in which case$$$ Privoxy

Announcing Privoxy 4.0.0 stable$$$--------------------------------------------------------------------$$$Privoxy 4.0.0 fixes a few minor bugs and comes with a couple of$$$general improvements and new features. HTTPS inspection is no$$$longer considered experimental.$$$$$$Two new features have been funded by donations. If you can;$$$please consider making a donation to support future improvements.$$$$$$--------------------------------------------------------------------$$$$$$Refer - https://www.privoxy.org/announce.txt

Announcing Privoxy 4.0.0 stable$$$--------------------------------------------------------------------$$$Privoxy 4.0.0 fixes a few minor bugs and comes with a couple of$$$general improvements and new features. HTTPS inspection is no$$$longer considered experimental.$$$$$$Two new features have been funded by donations. If you can;$$$please consider making a donation to support future improvements.$$$$$$--------------------------------------------------------------------$$$$$$Refer - https://www.privoxy.org/announce.txt

Privoxy 3.0.34 fixes a few minor bugs and comes with a couple of general improvements and new features.

Privoxy 3.0.34 fixes a few minor bugs and comes with a couple of general improvements and new features.