From git at git.privoxy.org Thu Jan 1 15:55:57 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:55:57 +0100 Subject: [Privoxy-commits] [privoxy] branch master updated (fcb5c5ad -> c47dd6b7) Message-ID: <176727935762.71466.13210995552465267910@privoxy-git> This is an automated email from the git hooks/post-receive script. git pushed a change to branch master in repository privoxy. from fcb5c5ad tests/cts/README: Recommend to use a curl upstream commit from today new ea6c68cc tests/cts/README: Recommend to use curl upstream tag rc-8_18_0-3 new dc9808c1 wolfssl: Spell 'wolfSSL' with uppercase 'SSL' in a warning new 68365439 Privoxy-Log-Parser: Bump version to 0.9.7 new 4437bce7 configure.in: Remove obsolete warning if OpenSSL is detected new d4b121f1 Privoxy-Log-Parser: Don't highlight the trailing period in a log message new 7004caa7 ChangeLog: Add changes for 4.1.0 stable new 41778f11 Update imdb filter to reduce the wasted space at the top of the page again new 59b7efa4 Bump copyright new ab4ba3df Bump copyright new 16142b99 configure: Bump version to 4.1.0 stable new 302d01af Bump SOURCE_DATE_EPOCH new f4b3a65d Bump copyright new 8770e57a Update SGML ChangeLog for Privoxy 4.1.0 new 8b1e3e4b Bump copyright new aa0940a9 Make spotify.com pattern more generic and add another test URL new 266206ac Bump copyright new e4a1d437 Bump copyright new 34f5dd39 Bump copyright new 0a39fe6e Bump copyright new 235bb3fb Regenerate AUTHORS new a24125b2 Regenerate config file for 4.1.0 stable new 84b69fab Bump SMGL entities for 4.1.0 stable new c47dd6b7 Rebuild docs for Privoxy 4.1.0 stable The 23 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: AUTHORS | 2 + ChangeLog | 153 ++++++++- INSTALL | 4 +- README | 4 +- config | 4 +- configure.in | 5 +- default.action.master | 6 +- default.filter | 4 +- doc/source/authors.sgml | 6 +- doc/source/changelog.sgml | 387 ++++++++++++---------- doc/source/config.sgml | 4 +- doc/source/copyright.sgml | 2 +- doc/source/developer-manual.sgml | 6 +- doc/source/faq.sgml | 6 +- doc/source/install.sgml | 6 +- doc/source/p-config.sgml | 2 +- doc/source/privoxy-man-page.sgml | 6 +- doc/source/readme.sgml | 8 +- doc/source/user-manual.sgml | 10 +- doc/source/webserver/index.sgml | 6 +- doc/webserver/developer-manual/documentation.html | 2 +- doc/webserver/developer-manual/index.html | 2 +- doc/webserver/developer-manual/newrelease.html | 18 +- doc/webserver/faq/copyright.html | 11 +- doc/webserver/faq/index.html | 4 +- doc/webserver/index.html | 2 +- doc/webserver/privoxy-index.html | 2 +- doc/webserver/user-manual/actions-file.html | 20 +- doc/webserver/user-manual/appendix.html | 23 +- doc/webserver/user-manual/config.html | 4 +- doc/webserver/user-manual/configuration.html | 8 +- doc/webserver/user-manual/contact.html | 4 +- doc/webserver/user-manual/copyright.html | 8 +- doc/webserver/user-manual/filter-file.html | 11 +- doc/webserver/user-manual/howto.html | 4 +- doc/webserver/user-manual/index.html | 6 +- doc/webserver/user-manual/installation.html | 8 +- doc/webserver/user-manual/introduction.html | 10 +- doc/webserver/user-manual/quickstart.html | 6 +- doc/webserver/user-manual/seealso.html | 4 +- doc/webserver/user-manual/startup.html | 8 +- doc/webserver/user-manual/templates.html | 4 +- doc/webserver/user-manual/whatsnew.html | 285 +++++++++------- tests/cts/README | 2 +- tools/privoxy-log-parser.pl | 4 +- wolfssl.c | 2 +- 46 files changed, 654 insertions(+), 439 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:01 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:01 +0100 Subject: [Privoxy-commits] [privoxy] 04/23: configure.in: Remove obsolete warning if OpenSSL is detected In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145559.1B1572B417@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 4437bce753fcb3b53a5c8d33b2397145284567e8 Author: Fabian Keil AuthorDate: Sun Dec 28 10:37:27 2025 +0100 configure.in: Remove 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 isn't needed and a Privoxy binary linked to OpenSSL can be distributed under the GPLv3 or later. --- configure.in | 1 - 1 file changed, 1 deletion(-) diff --git a/configure.in b/configure.in index a363a601..3dfe23d5 100644 --- a/configure.in +++ b/configure.in @@ -1238,7 +1238,6 @@ if test X"$OPT_OPENSSL" != Xno; then if test "x$FEATURE_HTTPS_INSPECTION_OPENSSL" = "xyes"; then AC_MSG_NOTICE([Detected OpenSSL. Enabling https inspection.]) - AC_MSG_WARN([If you intend to redistribute Privoxy, please make sure the "special exception" from section 3 of the GPLv2 applies.]) LIBS="$LIBS -lssl -lcrypto" old_CFLAGS_nospecial="$old_CFLAGS_nospecial" -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:00 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:00 +0100 Subject: [Privoxy-commits] [privoxy] 03/23: Privoxy-Log-Parser: Bump version to 0.9.7 In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145558.B7D172B415@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 683654393b7919485e3d18431b4ea2e2808dbf6d Author: Fabian Keil AuthorDate: Sat Dec 27 16:19:44 2025 +0100 Privoxy-Log-Parser: Bump version to 0.9.7 --- tools/privoxy-log-parser.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/privoxy-log-parser.pl b/tools/privoxy-log-parser.pl index a35030ff..f1052c01 100755 --- a/tools/privoxy-log-parser.pl +++ b/tools/privoxy-log-parser.pl @@ -43,7 +43,7 @@ use warnings; use Getopt::Long; use constant { - PRIVOXY_LOG_PARSER_VERSION => '0.9.6', + PRIVOXY_LOG_PARSER_VERSION => '0.9.7', # Feel free to mess with these ... DEFAULT_BACKGROUND => 'black', # Choose registered colour (like 'black') DEFAULT_TEXT_COLOUR => 'white', # Choose registered colour (like 'black') -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:55:58 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:55:58 +0100 Subject: [Privoxy-commits] [privoxy] 01/23: tests/cts/README: Recommend to use curl upstream tag rc-8_18_0-3 In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145558.4F05A2B39E@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit ea6c68cc7806d7e2ffb53058e18b2f75f0a9ed50 Author: Fabian Keil AuthorDate: Sat Dec 27 10:50:52 2025 +0100 tests/cts/README: Recommend to use curl upstream tag rc-8_18_0-3 --- tests/cts/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/cts/README b/tests/cts/README index 6259d131..82c6a508 100644 --- a/tests/cts/README +++ b/tests/cts/README @@ -10,7 +10,7 @@ Privoxy sources do: git clone https://github.com/curl/curl.git cd curl - git checkout -b cts-compatible-with-privoxy-tests d92e264ff0c15 + git checkout -b cts-compatible-with-privoxy-tests rc-8_18_0-3 # Build curl as described in GIT-INFO. Note that the configure # call needs to explicitly choose a TLS library. For example -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:55:59 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:55:59 +0100 Subject: [Privoxy-commits] [privoxy] 02/23: wolfssl: Spell 'wolfSSL' with uppercase 'SSL' in a warning In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145558.875722B3A0@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit dc9808c17ec321d425d3096a86fa50def79607c6 Author: Fabian Keil AuthorDate: Sat Dec 27 12:52:08 2025 +0100 wolfssl: Spell 'wolfSSL' with uppercase 'SSL' in a warning --- wolfssl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wolfssl.c b/wolfssl.c index 48899022..40a1a46f 100644 --- a/wolfssl.c +++ b/wolfssl.c @@ -1159,7 +1159,7 @@ extern int create_server_ssl_connection(struct client_state *csp) "Failed to enable 'Secure' Renegotiation. Continuing anyway."); } #else -#warning Looks like wolfssl has been compiled without HAVE_SECURE_RENEGOTIATION +#warning Looks like wolfSSL has been compiled without HAVE_SECURE_RENEGOTIATION #endif log_error(LOG_LEVEL_CONNECT, -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:04 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:04 +0100 Subject: [Privoxy-commits] [privoxy] 07/23: Update imdb filter to reduce the wasted space at the top of the page again In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145600.176AE2B41B@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 41778f11617019002d22e29953110be11175b28e Author: Fabian Keil AuthorDate: Thu Jan 1 00:48:24 2026 +0100 Update imdb filter to reduce the wasted space at the top of the page again --- default.filter | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/default.filter b/default.filter index d9e44b43..758814db 100644 --- a/default.filter +++ b/default.filter @@ -576,7 +576,7 @@ s@(]*@$1 style="display:none"@ +s@(
]*@
]*id="top_ad"[^>]*>.*@@ s@]*onload="doWithAds.call[^>]*>@@g -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:02 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:02 +0100 Subject: [Privoxy-commits] [privoxy] 05/23: Privoxy-Log-Parser: Don't highlight the trailing period in a log message In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145559.980E42B419@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit d4b121f1fb91329a592c525976cafde1901b1a9e Author: Fabian Keil AuthorDate: Sun Dec 28 17:21:21 2025 +0100 Privoxy-Log-Parser: Don't highlight the trailing period in a log message Fixes 3352cddf. --- tools/privoxy-log-parser.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/privoxy-log-parser.pl b/tools/privoxy-log-parser.pl index f1052c01..d45c4932 100755 --- a/tools/privoxy-log-parser.pl +++ b/tools/privoxy-log-parser.pl @@ -1539,7 +1539,7 @@ sub handle_loglevel_connect($) { # OK $c = highlight_matched_host($c, '(?<=connection from )[^ ]*'); $c = highlight_matched_pattern($c, 'Number', '(?<=socket )\d+'); - $c = highlight_matched_host($c, '(?<=through )[^ ]*'); + $c = highlight_matched_host($c, '(?<=through )[^ ]*(?=\.$)'); } elsif ($c =~ m/^Closing client socket/) { -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:03 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:03 +0100 Subject: [Privoxy-commits] [privoxy] 06/23: ChangeLog: Add changes for 4.1.0 stable In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145559.D5DAD2B41A@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 7004caa746ba9b3d67d2f2f6dd9538fe7d9e0b2a Author: Fabian Keil AuthorDate: Wed Dec 24 14:39:58 2025 +0100 ChangeLog: Add changes for 4.1.0 stable --- ChangeLog | 151 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 151 insertions(+) diff --git a/ChangeLog b/ChangeLog index a7bffc52..e0067e53 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,157 @@ -------------------------------------------------------------------- ChangeLog for Privoxy -------------------------------------------------------------------- +*** Version 4.1.0 stable *** + +- 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 doesn't (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 don't 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 isn't 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: Don't 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. + - Don't forward connection options Privoxy doesn't 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 we're 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 it's already part of csiz. While this was wrong it didn't + cause any actual problems as the buffer size is so large that + it didn't 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 + isn't Windows and doesn't have strerror(). Reported by Joshua Rogers. + - accept_connection(): Fix memory and socket leak if the server name and + port number ASCII decimal representation don't 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 previously would leak a couple of bytes of memory. + +- Action file improvements: + - Prevent a fingerprinting issue with various login pages by not handling + the requests as image requests or fast-redirecting them. Without the added + section a request to a blocked or redirected login URL could be misdetected + by third parties as the user being logged in to the given site, thus making + fingerprinting Privoxy users easier. Note that this does not prevent the + fingerprinting issue if the client is actually logged in. For details see: + https://robinlinus.github.io/socialmedia-leak/ + Doing that would probably be too invasive for a default configuration. + - Stop downgrading the HTTP version for port 631. It was supposed to work + around a problem with the CUPS webinterface but about 20 years later we + probably don't need it anymore ... + - Fix sticky actions for .flickr.com to match the action section. + - Remove an action section without an URL pattern. + - Disable fast-redirects for .bahn.de/ + - Disable fast-redirects for report.error-report.com/ + - Unblock metrics.1aeo.com/ + - Unblock .crates.io/ + - Block requests for mv.outbrain.com/ + - Disable filter{banners-by-size} for .jwz.org/ + - Disable deanimate-gifs for .githubusercontent.com/ + - Disable the banners-by-size filter for github.com + - Widen block pattern from 'metrics.' to '.metricts.' + - Add +server-header-tagger{content-type} to all standard settings. + +- Filter improvements: + - Update imdb filter to remove wasted space below the search field. + - Update bundeswehr.de filter to be effective again. + - Removed the obsolete ie-exploits filter. It didn't actually reliably + protect against Nimda, there never were active maintainers and IE is + obsolete anyway. Also some virus scanners seem to be offended by the + test case for the filter in the source tarball. + +- Privoxy-Log-Parser: + - Bumped version to 0.9.7. + - Fully highlight: Accepted connection from 127.0.0.1 on socket 9 connected through 127.0.1.1:8118. + - Highlight: Socket 8 timed out while waiting for client headers + - Highlight: 'Giving up draining socket 35.' + - Highlight: "Tagger 'http-method' didn't add tag 'POST': suppressed" + - Highlight: 'Skipped filter 'banners-by-size' after job number 1: match limit exceeded (-47)' + +- uagen: + - Bumped version to 0.1.7 + - Bumped BROWSER_VERSION and BROWSER_REVISION to match Firefox ESR 140. + +- Documentation: + - Updated license info to deal with wolfSSL's license change to GPLv3. + - Added new FAQ: 'Is the Privoxy source tarball infected by a virus?'. + - Removed claims that path matching can be turned case-sensitive. + The suggested method didsn't actually work. + +- Website improvements: + - GNUmakefile.in: Add a web-robots.txt target to only transfer the robots.txt to the SF server. + - robots.txt: Disallow /gitweb to hopefully reduce the load on the webserver + - robots.txt: Remvoe stray empty lines + - Added a vanity onion address for the privoxy.org onion service. + +- Tests: + - Updated test framework to work with recent (rc-8_18_0-3) cts upstream tests. + - tests/cts/run-privoxy-tests.sh: Pass arguments that follow "--" to + runtests-wrapper.sh so they can be passed to runtests.pl. + This allows to only run a single test without modifying the scripts: + ./run-privoxy-tests.sh -t upstream-tests -- 473 + - run-privoxy-tests.sh: Explicitly log if there were no errors. + - run-privoxy-tests.sh: Continue testing if a test in a test scenario fails. + - runtests-wrapper.sh: Explicitly set the path to the curl binary + using an absolute path. Otherwise runtests.pl uses a relative + path in its output which can be confusing. + - runtests-wrapper.sh: Improve a log message. + - Disable the forward-to-socks-proxy and forward-to-http-proxy scenarios + for now. Since curl commit d39db811929f the port randomisation can no + longer be disabled by the injected module so the tests don't work at the + moment. Discussion on the curl library mailinglist didn't result in + a solution (https://curl.se/mail/lib-2025-08/0000.html). + - tests/cts: Remove 'none' server section from tests. + It's no longer supported as of curl commit 71c9706959cb. + - run-privoxy-tests.sh: Print supported arguments in case of invalid ones. + - Add a test for the bundeswehr.de filter. + - tests/cts/gzip-compression/data/test13: Fix repetitive sequence by adding a missing %. + - Add a couple of tests for connection headers with keep-alive-timeout set. + - Add fetch test for the How-Tos in the user manual. + - ../privoxy-runtests.pm: Prevent warning if $_ is undefined. + - tests/cts/runtests-wrapper.sh: Stop explicitly setting HOSTIP. + It doesn't work with curl master at the moment. + - Let the "clean" target remove logs from the cts tests. + - .../content-filters/content-filters.action: Remove duplicate action section. + *** Version 4.0.0 stable *** - Bug fixes: -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:05 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:05 +0100 Subject: [Privoxy-commits] [privoxy] 08/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145600.9CC802B3A4@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 59b7efa446743b5c277a7f71dd5f5857444bd1c5 Author: Fabian Keil AuthorDate: Thu Jan 1 12:21:02 2026 +0100 Bump copyright --- default.filter | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/default.filter b/default.filter index 758814db..0f6a7dee 100644 --- a/default.filter +++ b/default.filter @@ -4,7 +4,7 @@ # # Purpose : Rules to process the content of web pages # -# Copyright : Written by and Copyright (C) 2001-2025 the +# Copyright : Written by and Copyright (C) 2001-2026 the # Privoxy team. https://www.privoxy.org/ # # This program is free software; you can redistribute it -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:06 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:06 +0100 Subject: [Privoxy-commits] [privoxy] 09/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145600.D089B2B41E@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit ab4ba3df1da1b01726c03011175fda784922a721 Author: Fabian Keil AuthorDate: Thu Jan 1 12:21:25 2026 +0100 Bump copyright --- doc/source/copyright.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/copyright.sgml b/doc/source/copyright.sgml index b324ddc4..486d0ff0 100644 --- a/doc/source/copyright.sgml +++ b/doc/source/copyright.sgml @@ -29,7 +29,7 @@ --> - Copyright &my-copy; 2001-2025 by Privoxy Developers privoxy-devel at lists.privoxy.org + Copyright &my-copy; 2001-2026 by Privoxy Developers privoxy-devel at lists.privoxy.org -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:07 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:07 +0100 Subject: [Privoxy-commits] [privoxy] 10/23: configure: Bump version to 4.1.0 stable In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145601.71F1D2B420@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 16142b999f1e00b2618cd84c7c98ba0dd4dfbec1 Author: Fabian Keil AuthorDate: Thu Jan 1 12:22:17 2026 +0100 configure: Bump version to 4.1.0 stable --- configure.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.in b/configure.in index 3dfe23d5..a97fff2e 100644 --- a/configure.in +++ b/configure.in @@ -81,7 +81,7 @@ dnl release and no new release is near. VERSION_MAJOR=4 VERSION_MINOR=1 VERSION_POINT=0 -CODE_STATUS="UNRELEASED" +CODE_STATUS="stable" dnl Timestamp (date +%s) used by the mtree-spec target. dnl Should be updated before releases but forgetting it isn't critical. -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:08 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:08 +0100 Subject: [Privoxy-commits] [privoxy] 11/23: Bump SOURCE_DATE_EPOCH In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145601.D56CA2B3A5@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 302d01af9156456c6724f1dcc5274d1df66c4a2b Author: Fabian Keil AuthorDate: Thu Jan 1 12:22:57 2026 +0100 Bump SOURCE_DATE_EPOCH --- configure.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.in b/configure.in index a97fff2e..5d2e3f37 100644 --- a/configure.in +++ b/configure.in @@ -85,7 +85,7 @@ CODE_STATUS="stable" dnl Timestamp (date +%s) used by the mtree-spec target. dnl Should be updated before releases but forgetting it isn't critical. -SOURCE_DATE_EPOCH=1735969800 +SOURCE_DATE_EPOCH=1767266508 dnl ================================================================= dnl Substitute the version numbers -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:09 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:09 +0100 Subject: [Privoxy-commits] [privoxy] 12/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145602.505B82B422@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit f4b3a65d351ca41487f34b57a2d62c91133567e0 Author: Fabian Keil AuthorDate: Thu Jan 1 13:43:37 2026 +0100 Bump copyright --- ChangeLog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index e0067e53..423adb34 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3827,7 +3827,7 @@ being a mix of "U.S. English", "U.K. English" and "Irish English". ---------------------------------------------------------------------- -Copyright : Written by and Copyright (C) 2001-2025 the +Copyright : Written by and Copyright (C) 2001-2026 the Privoxy team. https://www.privoxy.org/ Based on the Internet Junkbuster originally written -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:10 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:10 +0100 Subject: [Privoxy-commits] [privoxy] 13/23: Update SGML ChangeLog for Privoxy 4.1.0 In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145602.9FE6A2B3A7@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 8770e57a4a4a91d5aa0ef16218fb21ec086c64d2 Author: Fabian Keil AuthorDate: Thu Jan 1 13:56:15 2026 +0100 Update SGML ChangeLog for Privoxy 4.1.0 --- doc/source/changelog.sgml | 385 ++++++++++++++++++++++++++-------------------- 1 file changed, 215 insertions(+), 170 deletions(-) diff --git a/doc/source/changelog.sgml b/doc/source/changelog.sgml index 26f793d6..bc2d6e2f 100644 --- a/doc/source/changelog.sgml +++ b/doc/source/changelog.sgml @@ -24,216 +24,178 @@ --> - 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. + Privoxy 4.1.0 fixes a few + minor bugs and brings ZStandard-decompression support and + a couple of general improvements. - Two new features have been funded by donations. If you can, - please consider - making a donation - to support future improvements. - - - Changes in Privoxy 4.0.0 stable: + Changes in Privoxy 4.1.0 stable: - Bug fixes: + General improvements: - Add missing client-body-tagger data to the action_type_info[] struct - so lookups based on the action index work correctly again. - Prevents assertion failures or segfaults when trying to edit - an action file with the CGI editor. - The type of failure depended on whether or not assertions - were enabled and on whether or not Privoxy had been compiled - with FEATURE_EXTERNAL_FILTERS. - Regression introduced in Privoxy 3.0.34. - Patch submitted by Aaron Li in #940. + Add Zstandard-decompression support. - Bump MAX_FILTER_TYPES which should have been done in d128e6aa4 - when introducing the client-body-tagger{} action. - Prevents an assertion in cgi_edit_actions_for_url() from triggering - after e32d03e0 when using the CGI editor with assertions enabled. + compile_pattern(): Use pcre2_get_error_message() to provide better error messages. - is_untrusted_url(): Search the encrypted headers for the Referer - when the client is using https and https inspection is enabled. - Fixes the trust mechanism for https requests. - Reported by Laurent Caumont in #1767. + wolfssl: Use wolfTLS_client_method() instead of wolfSSLv23_method() + when creating the connection to the server. Allows to connect to + and https://traxxas.com/ while wolfSSLv23_method() + currently doesn't (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. - GNUMakefile.in: Let the install target work if no group is specified. + wolfssl: Warn if HAVE_SECURE_RENEGOTIATION is unavailable + and don't suggest to use HAVE_RENEGOTIATION_INDICATION instead. - GNUMakefile.in: Set GROUP_T when installing configuration files as root - and there is no privoxy user available so the install target doesn't - fail. Patch by Fabrice Fontaine. + show-status template: Add links for external (de)compression libraries. - GNUmakefile.in: Don't exit if configuration files are installed as root - as this can be considered acceptable when cross-compiling - Privoxy inside an autobuilder with only a root user. - Patch by Fabrice Fontaine. + If the server sends multiple Connection headers, only parse and + forward the first one. - configure.in: Fix argument types in gmtime_r() and localtime_r() probes. - Otherwise these probes always fail with stricter compilers - even if there is C library support for these functions. - Patch submitted by Florian Weimer in SF#149. + create_hexadecimal_hash_of_host(): Use snprintf() instead of sprint() + Silences a warning on OpenBSD. - Fix socks4 and socks4a support under glibc's source fortification. - With glibc's source fortification, gcc offers the compilation warning - resulting in a runtime abort() when using a socks4 or socks4a upstream proxy. - Despite the warning, the strlcpy() call in question is fine: gcc - misidentifies the size of the destination buffer, estimating to hold - only a single char while in fact the buffer stretches beyond the end of - the struct socks_op. - The issue was originally reported in the - NixOS - issue tracker prompted by an upgrade of glibc from 2.37-39 to 2.38-0. - Patch submitted by Ingo Blechschmid, joint work with - @esclear and @richi235. - - - - - - - - General improvements: - - - - Allow to use wolfSSL for https inspection. - wolfSSL supports TLS 1.3 and can be significantly faster than - mbedTLS. Mainly tested on ElectroBSD amd64 where it can - compete - with OpenSSL and LibreSSL - To enable the support, install wolfSSL and run ./configure - with the --with-wolfssl option. - Sponsored by Privoxy project funds collected at SPI. + Also log the listening address and port the request came in on. - Add an test framework that leverages the curl test suite. - Sponsored by Privoxy project funds collected at SPI. + Added periods to a couple of log messages. - Add pcre2 support. Closes bug #935. - Initial patch submitted by Gagan Sidhu. + Removed support for pcre1. - Use SHA256 as hash algorithm for the certificate and key file names - instead of MD5. The known MD5 vulnerabilities shouldn't matter for - Privoxy's use case but it doesn't hurt to use a hash algorithm that - isn't deprecated. - Sponsored by: Robert Klemme + 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 isn't needed + and a Privoxy binary linked to OpenSSL can be distributed under the + GPLv3 or later. - Add support for mbedTLS 3.x. This removes a sanity check - (whether issuer key and issuer certificate match) that seems - overly cautious and fails to compile with mbedTLS 3.x as the - struct members are private. We don't have an equivalent check - in the OpenSSL or wolfSSL code either. + init_domain_components(): Assert that the http->dbuffer and http->dvec + are NULL to detect memory leaks earlier. - + + + + + + + Bug fixes: + - Factor out newer_privoxy_version_required() and improve the logic - Previously 3.0.11 was considered newer than 4.0.0. + openssl: Don't 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. - init_error_log(): Include the reason for failures to open the log file. + Don't forward connection options Privoxy doesn't understand. - create_client_ssl_connection(): Don't keep the certificate lock - longer than necessary. + 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". - Add periods to a bunch of log messages. + If the MS IIS5 hack fails, only send the error response if we're buffering content + Previously the error response was also sent if the client already + received the HTTP headers from the server. - normalize_lws(): Only log the 'Reducing whitespace ...' message - once per header + Fix compilation when configured with --disable-ipv6-support. + Submitted by Luca Broglio. - log_error() Win32: Only call LogShowActivity() for debug level - LOG_LEVEL_REQUEST. As of b94bbe62a950, which was part of Privoxy 3.0.29, - LOG_LEVEL_REQUEST is used for all requests including crunched ones. - Previously LogShowActivity() was called twice for crunched - requests, (presumably) resulting in an aborted animation. + Fixed detection and use of pcre2.h from a subdirectory. + SF bug #946. Patch submitted by Jakub Kulik. - Remove ./ prefix from tarball-dist files. + Properly handle IPv6 addresses in the Host header. + Reported by Joshua Rogers. - create_client_ssl_connection(): Make it more obvious from an - error message that a function failed. + socks4_connect(): Fix the dstsize passed to strlcpy() in case of socks4a. + Previously Privoxy would substract sizeof(struct socks_op) twice + as it's already part of csiz. While this was wrong it didn't + cause any actual problems as the buffer size is so large that + it didn't matter. Reported by Joshua Rogers. - Use stringify() instead of section_target() and remove section_target(). - Like the XXX comment suggested this could be done my moving the hash - into the templates which seems preferable anyway. + error_response(): Prevent a theoretical memory leak. Reported by Joshua Rogers. - Prevent some compiler warnings. + log_error(): Fix a segmentation fault when logging %E on a platform that + isn't Windows and doesn't have strerror(). Reported by Joshua Rogers. - parse_numeric_value(): Expect a base-ten number. + accept_connection(): Fix memory and socket leak if the server name and + port number ASCII decimal representation don't fit. This is not expected + to happen. Reported by Joshua Rogers. - windows/MYconfigure: Have gcc diagnostics in color. + 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 previously would leak a couple of bytes of memory. @@ -245,99 +207,106 @@ - Block requests to .amazon-adsystem.com/ - - - - - Block requests to 0.css-load.com/ + Prevent a fingerprinting issue with various login pages by not handling + the requests as image requests or fast-redirecting them. Without the added + section a request to a blocked or redirected login URL could be misdetected + by third parties as the user being logged in to the given site, thus making + fingerprinting Privoxy users easier. Note that this does not prevent the + fingerprinting issue if the client is actually logged in. For details see + https://robinlinus.github.io/socialmedia-leak/. + Doing that would probably be too invasive for a default configuration. - Block requests to html-load.com/ and 1.html-load.com/ + Stop downgrading the HTTP version for port 631. It was supposed to work + around a problem with the CUPS webinterface but about 20 years later we + probably don't need it anymore ... - Block requests to b.6sc.co/ + Fix sticky actions for .flickr.com to match the action section. - Block requests to i.clean.gg/ + Remove an action section without an URL pattern. - Block requests to s.cpx.to/ + Disable fast-redirects for .bahn.de/ - Block requests to track.venatusmedia.com/ + Disable fast-redirects for report.error-report.com/ - Block requests to secure-eu.nmrodam.com/ + Unblock metrics.1aeo.com/ - Block requests to o2.mouseflow.com/ + Unblock .crates.io/ - Disable fast-redirects for services.akteneinsichtsportal.de/ + Block requests for mv.outbrain.com/ - Disable fast-redirects for /wp-content/plugins/pdf-viewer-for-elementor + Disable filter{banners-by-size} for .jwz.org/ - Disable fast-redirects for syndication.twitter.com/ + Disable deanimate-gifs for .githubusercontent.com/ - Disable fast-redirects for archive.softwareheritage.org/ + Disable the banners-by-size filter for github.com - Disable fast-redirects to duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ + Widen block pattern from 'metrics.' to '.metricts.' - Disable fast-redirects for .creator-spring.com/_next/image + Add +server-header-tagger{content-type} to all standard settings. - - - - Disable fast redirects for accounts.bahn.de/ - - + + + + + + + Filter improvements: + - Unblock .datenschmutz.de/ + Update imdb filter to remove wasted space below the search field. - Unblock requests for 'adventur*.' + Update bundeswehr.de filter to be effective again. - Unblock adl.windows.com/ - as it is apparently required to update from Windows 10 to 11. - Reported by Sam Varshavchik. + Removed the obsolete ie-exploits filter. It didn't actually reliably + protect against Nimda, there never were active maintainers and IE is + obsolete anyway. Also some virus scanners seem to be offended by the + test case for the filter in the source tarball. @@ -349,27 +318,49 @@ - Highlight 'Couldn't deliver the error message for [...]'. + Bumped version to 0.9.7. - Highlight 'Failed to accept() incoming connection: Software caused connection abort'. + Fully highlight: Accepted connection from 127.0.0.1 on socket 9 connected through 127.0.1.1:8118. - Highlight 'Keeping chunk offset at 0 despite flushing 31 bytes.'. + Highlight: Socket 8 timed out while waiting for client headers - Highlight 'Not shutting down client connection on socket 8. The socket is no longer alive.'. + Highlight: 'Giving up draining socket 35.' + + + + + Highlight: "Tagger 'http-method' didn't add tag 'POST': suppressed" + + + + + Highlight: 'Skipped filter 'banners-by-size' after job number 1: match limit exceeded (-47)' + + + + + + + + uagen: + + + + Bumped version to 0.1.7 - Bump version to 0.9.6. + Bumped BROWSER_VERSION and BROWSER_REVISION to match Firefox ESR 140. @@ -377,22 +368,22 @@ - Privoxy-Regression-Test.pl: + Documentation: - Let the --min-level option increase the --max-level - if the latter is smaller than the former. + Updated license info to deal with wolfSSL's license change to GPLv3. - Add --curl option to use a non-default curl binary. + Added new FAQ: 'Is the Privoxy source tarball infected by a virus?'. - Bump version to 0.7.5. + Removed claims that path matching can be turned case-sensitive. + The suggested method didsn't actually work. @@ -400,75 +391,129 @@ - uagen: + Website improvements: - Bump BROWSER_VERSION and BROWSER_REVISION to match Firefox ESR 128. + GNUmakefile.in: Add a web-robots.txt target to only transfer the robots.txt to the SF server. - Bump version to 1.2.6. + robots.txt: Disallow /gitweb to hopefully reduce the load on the webserver - + + + + robots.txt: Remvoe stray empty lines + + + + + Added a vanity onion address for the privoxy.org onion service. + + - Documentation: + Tests: - Add HOWTOs for https inspection and client-tags to user-manual. + Updated test framework to work with recent (rc-8_18_0-3) cts upstream tests. + + + + + tests/cts/run-privoxy-tests.sh: Pass arguments that follow "--" to + runtests-wrapper.sh so they can be passed to runtests.pl. + This allows to only run a single test without modifying the scripts: + ./run-privoxy-tests.sh -t upstream-tests -- 473 + + + + + run-privoxy-tests.sh: Explicitly log if there were no errors. + + + + + run-privoxy-tests.sh: Continue testing if a test in a test scenario fails. + + + + + runtests-wrapper.sh: Explicitly set the path to the curl binary + using an absolute path. Otherwise runtests.pl uses a relative + path in its output which can be confusing. + + + + + runtests-wrapper.sh: Improve a log message. + + + + + Disable the forward-to-socks-proxy and forward-to-http-proxy scenarios + for now. Since curl commit d39db811929f the port randomisation can no + longer be disabled by the injected module so the tests don't work at the + moment. Discussion on the curl library mailinglist didn't result in + a solution (https://curl.se/mail/lib-2025-08/0000.html). + + + + + tests/cts: Remove 'none' server section from tests. + It's no longer supported as of curl commit 71c9706959cb. + + + + + run-privoxy-tests.sh: Print supported arguments in case of invalid ones. - Suggest to use the force-text-mode action when filtering binary content - with external filters. + Add a test for the bundeswehr.de filter. - Declare https-inspection non-experimental. + tests/cts/gzip-compression/data/test13: Fix repetitive sequence by adding a missing %. - FAQ: Mention that - Privoxy - Moral Licenses are available as well. + Add a couple of tests for connection headers with keep-alive-timeout set. - Fix LibreSSL URL. + Add fetch test for the How-Tos in the user manual. - Update perlre perldoc URL. + ../privoxy-runtests.pm: Prevent warning if $_ is undefined. - config: Add SOCKS 5 to the list of supported protocols. + tests/cts/runtests-wrapper.sh: Stop explicitly setting HOSTIP. + It doesn't work with curl master at the moment. - In the Windows build section, note that one only needs tidy - to build the docs. If you're not building the docbook stuff you - don't need tidy. + Let the "clean" target remove logs from the cts tests. - trust: Use the words 'allowlists' and 'blocklists' - instead of "whitelists" and "blacklists" which some - people consider to be less inclusive. + .../content-filters/content-filters.action: Remove duplicate action section. -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:11 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:11 +0100 Subject: [Privoxy-commits] [privoxy] 14/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145602.D7BB12B424@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 8b1e3e4b274bb30df57df4d72769af01cb41f4d0 Author: Fabian Keil AuthorDate: Thu Jan 1 13:56:30 2026 +0100 Bump copyright --- doc/source/changelog.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/changelog.sgml b/doc/source/changelog.sgml index bc2d6e2f..4da766e4 100644 --- a/doc/source/changelog.sgml +++ b/doc/source/changelog.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - Copyright (C) 2013-2025 Privoxy Developers https://www.privoxy.org/ + Copyright (C) 2013-2026 Privoxy Developers https://www.privoxy.org/ See LICENSE. ====================================================================== -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:12 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:12 +0100 Subject: [Privoxy-commits] [privoxy] 15/23: Make spotify.com pattern more generic and add another test URL In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145603.489EC2B3AA@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit aa0940a9791cbb621018a983d17355e7e0e74d39 Author: Fabian Keil AuthorDate: Thu Jan 1 15:27:00 2026 +0100 Make spotify.com pattern more generic and add another test URL --- default.action.master | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/default.action.master b/default.action.master index ae2eba7b..722497b7 100644 --- a/default.action.master +++ b/default.action.master @@ -2773,9 +2773,9 @@ plus.google.com/up/accounts/upgrade/\? # URL = https://login.skype.com/login?message=signin_continue&redirect_uri=https%3A%2F%2Fsecure.skype.com%2Ffavicon.ico login.skype.com/login\? # URL = https://www.spotify.com/en/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico +# URL = https://www.spotify.com/de/en/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico # URL = http://www.spotify.com/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico -www.spotify.com/[^/]+/login/\? -www.spotify.com/login/\? +www.spotify.com/.*/login/\? # URL = https://www.reddit.com/login?dest=https%3A%2F%2Fwww.reddit.com%2Ffavicon.ico # URL = https://www.reddit.com/login/?dest=https%3A%2F%2Fwww.reddit.com%2Ffavicon.ico www.reddit.com/login -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:13 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:13 +0100 Subject: [Privoxy-commits] [privoxy] 16/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145603.851D82B3AB@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 266206acdebf33e9548a16f289013cef4e0d725f Author: Fabian Keil AuthorDate: Thu Jan 1 15:27:22 2026 +0100 Bump copyright --- default.action.master | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/default.action.master b/default.action.master index 722497b7..6c8e8d82 100644 --- a/default.action.master +++ b/default.action.master @@ -21,7 +21,7 @@ # and enhancements are better placed in user.action, # the match-all section has been moved to match-all.action. # -# Copyright : Written by and Copyright (C) 2001-2025 the +# Copyright : Written by and Copyright (C) 2001-2026 the # Privoxy team. https://www.privoxy.org/ # # Feedback welcome, for details please have a look at: -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:14 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:14 +0100 Subject: [Privoxy-commits] [privoxy] 17/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145603.EA0D62B427@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit e4a1d437bb65cbbb338a0246cb92a2271b4b551c Author: Fabian Keil AuthorDate: Thu Jan 1 15:37:03 2026 +0100 Bump copyright --- doc/source/p-config.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 95d1e52d..cca2fd32 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -90,7 +90,7 @@ Sample Configuration File for Privoxy &p-version; -Copyright (C) 2001-2025 Privoxy Developers https://www.privoxy.org/ +Copyright (C) 2001-2026 Privoxy Developers https://www.privoxy.org/ -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:15 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:15 +0100 Subject: [Privoxy-commits] [privoxy] 18/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145604.582BC2B3AC@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 34f5dd39e64f6859cc3a01ee396dc71f7cd24d0c Author: Fabian Keil AuthorDate: Thu Jan 1 15:44:25 2026 +0100 Bump copyright --- doc/source/readme.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/readme.sgml b/doc/source/readme.sgml index f2dbd1e4..2ee0c90c 100644 --- a/doc/source/readme.sgml +++ b/doc/source/readme.sgml @@ -78,7 +78,7 @@ * * Purpose : Give a short intro about Privoxy. * - * Copyright : Written by and Copyright (C) 2001-2021 the + * Copyright : Written by and Copyright (C) 2001-2026 the * Privoxy team. https://www.privoxy.org/ * * Based on the Internet Junkbuster originally written -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:16 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:16 +0100 Subject: [Privoxy-commits] [privoxy] 19/23: Bump copyright In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145604.ADF942B42A@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 0a39fe6e638a176346ebcd524c384ec5ec7e0398 Author: Fabian Keil AuthorDate: Thu Jan 1 15:48:19 2026 +0100 Bump copyright --- doc/source/user-manual.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index 1427950b..ff80dc5e 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -35,7 +35,7 @@ Purpose : user manual - Copyright (C) 2001-2025 Privoxy Developers https://www.privoxy.org/ + Copyright (C) 2001-2026 Privoxy Developers https://www.privoxy.org/ See LICENSE. ======================================================================== @@ -54,7 +54,7 @@ - Copyright &my-copy; 2001-2025 by + Copyright &my-copy; 2001-2026 by Privoxy Developers -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:17 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:17 +0100 Subject: [Privoxy-commits] [privoxy] 20/23: Regenerate AUTHORS In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145604.E35812B3AE@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 235bb3fbdca091ee2b1f4e51dbfe6500323ef56f Author: Fabian Keil AuthorDate: Thu Jan 1 15:27:36 2026 +0100 Regenerate AUTHORS --- AUTHORS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AUTHORS b/AUTHORS index f8e5b2d1..a51610df 100644 --- a/AUTHORS +++ b/AUTHORS @@ -58,6 +58,7 @@ include (in alphabetical order): David Bo Gergely Bor Francois Botha + Luca Broglio Reiner Buehl Burberry Calestyo @@ -124,6 +125,7 @@ include (in alphabetical order): Max Khon Steven Kolins Korda + Jakub Kulik Stefan Kurtz Zeno Kugy David Laight -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:18 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:18 +0100 Subject: [Privoxy-commits] [privoxy] 21/23: Regenerate config file for 4.1.0 stable In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145605.2C8AE2B42C@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit a24125b21e8a6906011933c49052e606c9c100c0 Author: Fabian Keil AuthorDate: Thu Jan 1 15:37:52 2026 +0100 Regenerate config file for 4.1.0 stable --- config | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config b/config index 8f358f57..cea37352 100644 --- a/config +++ b/config @@ -1,6 +1,6 @@ -# Sample Configuration File for Privoxy 4.0.0 +# Sample Configuration File for Privoxy 4.1.0 # -# Copyright (C) 2001-2025 Privoxy Developers https://www.privoxy.org/ +# Copyright (C) 2001-2026 Privoxy Developers https://www.privoxy.org/ # ##################################################################### # # -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:19 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:19 +0100 Subject: [Privoxy-commits] [privoxy] 22/23: Bump SMGL entities for 4.1.0 stable In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145605.A26C22B3AF@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 84b69fabf3d096a18ef5b3bf4da45e40a9a06438 Author: Fabian Keil AuthorDate: Thu Jan 1 15:41:59 2026 +0100 Bump SMGL entities for 4.1.0 stable --- doc/source/authors.sgml | 6 +++--- doc/source/config.sgml | 4 ++-- doc/source/developer-manual.sgml | 6 +++--- doc/source/faq.sgml | 6 +++--- doc/source/install.sgml | 6 +++--- doc/source/privoxy-man-page.sgml | 6 +++--- doc/source/readme.sgml | 6 +++--- doc/source/user-manual.sgml | 6 +++--- doc/source/webserver/index.sgml | 6 +++--- 9 files changed, 26 insertions(+), 26 deletions(-) diff --git a/doc/source/authors.sgml b/doc/source/authors.sgml index d7b21628..8e0d0d22 100644 --- a/doc/source/authors.sgml +++ b/doc/source/authors.sgml @@ -24,9 +24,9 @@ - - - + + + ]> diff --git a/doc/source/config.sgml b/doc/source/config.sgml index fb76ec4d..bb3252cb 100644 --- a/doc/source/config.sgml +++ b/doc/source/config.sgml @@ -2,8 +2,8 @@ - - + + Privoxy"> diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 8f48814c..d31ccc03 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -6,9 +6,9 @@ - - - + + + diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 8fc8fa77..e81adc47 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -9,9 +9,9 @@ - - - + + + diff --git a/doc/source/install.sgml b/doc/source/install.sgml index f0c68e11..165e3367 100644 --- a/doc/source/install.sgml +++ b/doc/source/install.sgml @@ -2,9 +2,9 @@ - - - + + + diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index d1f68d13..ce5a8215 100644 --- a/doc/source/privoxy-man-page.sgml +++ b/doc/source/privoxy-man-page.sgml @@ -39,9 +39,9 @@ - - - + + + diff --git a/doc/source/readme.sgml b/doc/source/readme.sgml index 2ee0c90c..1edda49f 100644 --- a/doc/source/readme.sgml +++ b/doc/source/readme.sgml @@ -5,9 +5,9 @@ - - - + + + diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index ff80dc5e..4a6d5003 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -15,10 +15,10 @@ - + - - + + diff --git a/doc/source/webserver/index.sgml b/doc/source/webserver/index.sgml index ea7b4f90..6e4b2826 100644 --- a/doc/source/webserver/index.sgml +++ b/doc/source/webserver/index.sgml @@ -6,9 +6,9 @@ - - - + + + -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 16:01:09 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 16:01:09 +0100 Subject: [Privoxy-commits] [privoxy] branch master updated: Adjust spotify.com pattern again so the tests actually pass Message-ID: <176727966965.29.5846572647139719805@privoxy-git> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. The following commit(s) were added to refs/heads/master by this push: new b8380ccc Adjust spotify.com pattern again so the tests actually pass b8380ccc is described below commit b8380ccc634516f96fdf07e3b6b445d6fd8dcb76 Author: Fabian Keil AuthorDate: Thu Jan 1 16:01:14 2026 +0100 Adjust spotify.com pattern again so the tests actually pass --- default.action.master | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/default.action.master b/default.action.master index 6c8e8d82..9caa602c 100644 --- a/default.action.master +++ b/default.action.master @@ -2775,7 +2775,7 @@ login.skype.com/login\? # URL = https://www.spotify.com/en/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico # URL = https://www.spotify.com/de/en/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico # URL = http://www.spotify.com/login/?forward_url=https%3A%2F%2Fwww.spotify.com%2Ffavicon.ico -www.spotify.com/.*/login/\? +www.spotify.com/.*login/\? # URL = https://www.reddit.com/login?dest=https%3A%2F%2Fwww.reddit.com%2Ffavicon.ico # URL = https://www.reddit.com/login/?dest=https%3A%2F%2Fwww.reddit.com%2Ffavicon.ico www.reddit.com/login -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Thu Jan 1 15:56:20 2026 From: git at git.privoxy.org (User Git) Date: Thu, 01 Jan 2026 15:56:20 +0100 Subject: [Privoxy-commits] [privoxy] 23/23: Rebuild docs for Privoxy 4.1.0 stable In-Reply-To: <176727935762.71466.13210995552465267910@privoxy-git> References: <176727935762.71466.13210995552465267910@privoxy-git> Message-ID: <20260101145607.AB8632B3B1@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit c47dd6b78cb0bcd85d4b7a2fbc905cc77946005e Author: Fabian Keil AuthorDate: Thu Jan 1 15:55:14 2026 +0100 Rebuild docs for Privoxy 4.1.0 stable --- INSTALL | 4 +- README | 4 +- doc/webserver/developer-manual/documentation.html | 2 +- doc/webserver/developer-manual/index.html | 2 +- doc/webserver/developer-manual/newrelease.html | 18 +- doc/webserver/faq/copyright.html | 11 +- doc/webserver/faq/index.html | 4 +- doc/webserver/index.html | 2 +- doc/webserver/privoxy-index.html | 2 +- doc/webserver/user-manual/actions-file.html | 20 +- doc/webserver/user-manual/appendix.html | 23 +- doc/webserver/user-manual/config.html | 4 +- doc/webserver/user-manual/configuration.html | 8 +- doc/webserver/user-manual/contact.html | 4 +- doc/webserver/user-manual/copyright.html | 8 +- doc/webserver/user-manual/filter-file.html | 11 +- doc/webserver/user-manual/howto.html | 4 +- doc/webserver/user-manual/index.html | 6 +- doc/webserver/user-manual/installation.html | 8 +- doc/webserver/user-manual/introduction.html | 10 +- doc/webserver/user-manual/quickstart.html | 6 +- doc/webserver/user-manual/seealso.html | 4 +- doc/webserver/user-manual/startup.html | 8 +- doc/webserver/user-manual/templates.html | 4 +- doc/webserver/user-manual/whatsnew.html | 285 ++++++++++++---------- 25 files changed, 240 insertions(+), 222 deletions(-) diff --git a/INSTALL b/INSTALL index b597ec5d..cd16ffd8 100644 --- a/INSTALL +++ b/INSTALL @@ -39,8 +39,8 @@ compiler like gcc are required. When building from a source tarball, first unpack the source: - tar xzvf privoxy-4.0.0-stable-src.tar.gz - cd privoxy-4.0.0-stable + tar xzvf privoxy-4.1.0-stable-src.tar.gz + cd privoxy-4.1.0-stable To build the development version, you can get the source code by doing: diff --git a/README b/README index f796b56c..0e095d31 100644 --- a/README +++ b/README @@ -4,7 +4,7 @@ * * Purpose : Give a short intro about Privoxy. * - * Copyright : Written by and Copyright (C) 2001-2021 the + * Copyright : Written by and Copyright (C) 2001-2026 the * Privoxy team. https://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -32,7 +32,7 @@ * *********************************************************************/ -This README is included with Privoxy 4.0.0. See https://www.privoxy.org/ for +This README is included with Privoxy 4.1.0. See https://www.privoxy.org/ for more information. The current code maturity level is "stable". ------------------------------------------------------------------------------- diff --git a/doc/webserver/developer-manual/documentation.html b/doc/webserver/developer-manual/documentation.html index 6a6386c0..254c187c 100644 --- a/doc/webserver/developer-manual/documentation.html +++ b/doc/webserver/developer-manual/documentation.html @@ -236,7 +236,7 @@ p-version: the Privoxy version string, e.g. "4.0.0". + "APPLICATION">Privoxy version string, e.g. "4.1.0". p-status: the project status, either diff --git a/doc/webserver/developer-manual/index.html b/doc/webserver/developer-manual/index.html index dc19bd3b..e55963c0 100644 --- a/doc/webserver/developer-manual/index.html +++ b/doc/webserver/developer-manual/index.html @@ -22,7 +22,7 @@ helpful!) reading for anyone who wants to join the team. Note that it's currently out of date and may not be entirely correct. As always, patches are welcome.

Please note that this document is constantly evolving. This copy represents the state at the release of - version 4.0.0. You can find the latest version of the this manual at https://www.privoxy.org/developer-manual/. Please have a look at the contact section in the user manual if you are interested in contacting the developers.

diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index f8ff3799..d2cefca1 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -463,7 +463,7 @@
- 
  dch -v 4.0.0-1
+ 
  dch -v 4.1.0-1
@@ -480,7 +480,7 @@
- 
  lintian -iI ../build-area/privoxy_4.0.0-1_amd64.changes
+ 
  lintian -iI ../build-area/privoxy_4.1.0-1_amd64.changes
@@ -489,7 +489,7 @@ 
  sudo cowbuilder --build --basepath /var/cache/pbuilder/base.cow ../build-area/privoxy_4.0.0-1.dsc
+ "PROGRAMLISTING"> sudo cowbuilder --build --basepath /var/cache/pbuilder/base.cow ../build-area/privoxy_4.1.0-1.dsc @@ -498,19 +498,19 @@ 
  autopkgtest /var/cache/pbuilder/result/privoxy_4.0.0-1_amd64.changes -s -- schroot sid
+ "PROGRAMLISTING"> autopkgtest /var/cache/pbuilder/result/privoxy_4.1.0-1_amd64.changes -s -- schroot sid

Or just push the changes to salsa.debian.org, where a CI pipeline is defined for the package, that builds and tests it.

If everything is okay, run cowbuilder with i386 and amd64 environments for current Debian stable release and - build privoxy_4.0.0-1_i386.deb and privoxy_4.0.0-1_amd64.deb. Then sign both files:

+ build privoxy_4.1.0-1_i386.deb and privoxy_4.1.0-1_amd64.deb. Then sign both files:

- 
  gpg --detach-sign --armor privoxy_4.0.0-1_i386.deb
-  gpg --detach-sign --armor privoxy_4.0.0-1_amd64.deb
+ 
  gpg --detach-sign --armor privoxy_4.1.0-1_i386.deb
+  gpg --detach-sign --armor privoxy_4.1.0-1_amd64.deb
@@ -626,8 +626,8 @@

6.5. Updating the RSS feed

Once the packages are uploaded to SourceForge they should be mirrored on the Privoxy websites (https://www.privoxy.org/ and http://l3tczdiiwoo63iwxty4lhs6p7eaxop5micbn7vbliydgv63x5zrrrfyd.onion/). This is usually done by + "http://privoxy5wtwbtk4wwyrdbg6oxeghvhghghmokcx2iawydkqmaztfbbid.onion/" target= + "_top">http://privoxy5wtwbtk4wwyrdbg6oxeghvhghghmokcx2iawydkqmaztfbbid.onion/). This is usually done by Fabian who uses a couple of shell functions for this that aren't documented or published yet.

Once the packages are uploaded to the mirror the RSS feed has to be regenerated with a command like:

diff --git a/doc/webserver/faq/copyright.html b/doc/webserver/faq/copyright.html index a855fcaa..e6a6820c 100644 --- a/doc/webserver/faq/copyright.html +++ b/doc/webserver/faq/copyright.html @@ -25,7 +25,7 @@

7. Privoxy Copyright, License and History

-

Copyright © 2001-2025 by Privoxy Developers

Privoxy 4.0.0 User ManualPrivoxy 4.1.0 User Manual
Prev