X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fannounce.txt;h=21908e1bdf4f39ac7e21881d0dd2f3924c4e960e;hp=fa042c33158a7b9384f4fd311d416e82efc8f72b;hb=ee9106f380afd507cb746e2c4c62085ecdc414b2;hpb=dc7dcbfe59e957f7b636f2b1c6f9516735d47a1d diff --git a/doc/webserver/announce.txt b/doc/webserver/announce.txt index fa042c33..21908e1b 100644 --- a/doc/webserver/announce.txt +++ b/doc/webserver/announce.txt @@ -1,376 +1,310 @@ - Announcing Privoxy v.3.0.19 stable + Announcing Privoxy 3.0.30 stable -------------------------------------------------------------------- -This is a bug-fix release for the previously released -Privoxy 3.0.18. One of the fixes addresses a security issue. +Privoxy 3.0.30 stable fixes a couple of bugs and introduces +a few new features. -------------------------------------------------------------------- -ChangeLog for Privoxy +ChangeLog for Privoxy 3.0.30 -------------------------------------------------------------------- -*** Version 3.0.19 Stable *** - Bug fixes: - - Prevent a segmentation fault when de-chunking buffered content. - It could be triggered by malicious web servers if Privoxy was - configured to filter the content and running on a platform - where SIZE_T_MAX isn't larger than UINT_MAX, which probably - includes most 32-bit systems. On those platforms, all Privoxy - versions before 3.0.19 appear to be affected. - To be on the safe side, this bug should be presumed to allow - code execution as proving that it doesn't seems unrealistic. - - Do not expect a response from the SOCKS4/4A server until it - got something to respond to. This regression was introduced - in 3.0.18 and prevented the SOCKS4/4A negotiation from working. - Reported by qqqqqw in #3459781. + - 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. + - 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: - - Fix an off-by-one in an error message about connect failures. - - Use a GNUMakefile variable for the webserver root directory and - update the path. Sourceforge changed it which broke various - web-related targets. - - Update the CODE_STATUS description. - -*** Version 3.0.18 stable *** - -- Bug fixes: - - If a generated redirect URL contains characters RFC 3986 doesn't - permit, they are (re)encoded. Not doing this makes Privoxy versions - from 3.0.5 to 3.0.17 susceptible to HTTP response splitting (CWE-113) - attacks if the +fast-redirects{check-decoded-url} action is used. - - Fix a logic bug that could cause Privoxy to reuse a server - socket after it got tainted by a server-header-tagger-induced - block that was triggered before the whole server response had - been read. If keep-alive was enabled and the request following - the blocked one was to the same host and using the same forwarding - settings, Privoxy would send it on the tainted server socket. - While the server would simply treat it as a pipelined request, - Privoxy would later on fail to properly parse the server's - response as it would try to parse the unread data from the - first response as server headers for the second one. - Regression introduced in 3.0.17. - - When implying keep-alive in client_connection(), remember that - the client didn't. Fixes a regression introduced in 3.0.13 that - would cause Privoxy to wait for additional client requests after - receiving a HTTP/1.1 request with "Connection: close" set - and connection sharing enabled. - With clients which terminates the client connection after detecting - that the whole body has been received it doesn't really matter, - but with clients that don't the connection would be kept open until - it timed out. - - Fix a subtle race condition between prepare_csp_for_next_request() - and sweep(). A thread preparing itself for the next client request - could briefly appear to be inactive. - If all other threads were already using more recent files, - the thread could get its files swept away under its feet. - So far this has only been reproduced while stress testing in - valgrind while touching action files in a loop. It's unlikely - to have caused any actual problems in the real world. - - Disable filters if SDCH compression is used unless filtering is forced. - If SDCH was combined with a supported compression algorithm, Privoxy - previously could try to decompress it and ditch the Content-Encoding - header even though the SDCH compression wasn't dealt with. - Reported by zebul666 in #3225863. - - Make a copy of the --user value and only mess with that when splitting - user and group. On some operating systems modifying the value directly - is reflected in the output of ps and friends and can be misleading. - Reported by zepard in #3292710. - - If forwarded-connect-retries is set, only retry if Privoxy is actually - forwarding the request. Previously direct connections would be retried - as well. - - Fixed a small memory leak when retrying connections with IPv6 - support enabled. - - Remove an incorrect assertion in compile_dynamic_pcrs_job_list() - It could be triggered by a pcrs job with an invalid pcre - pattern (for example one that contains a lone quantifier). - - If the --user argument user[.group] contains a dot, always bail out - if no group has been specified. Previously the intended, but undocumented - (and apparently untested), behaviour was to try interpreting the whole - argument as user name, but the detection was flawed and checked for '0' - instead of '\0', thus merely preventing group names beginning with a zero. - - In html_code_map[], use a numeric character reference instead of ' - which wasn't standardized before XHTML 1.0. - - Fix an invalid free when compiled with FEATURE_GRACEFUL_TERMINATION - and shut down through http://config.privoxy.org/die - - In get_actions(), fix the "temporary" backwards compatibility hack - to accept block actions without reason. - It also covered other actions that should be rejected as invalid. - Reported by Billy Crook. - -- General improvements: - - Privoxy can (re)compress buffered content before delivering - it to the client. Disabled by default as most users wouldn't - benefit from it. - - The +fast-redirects{check-decoded-url} action checks URL - segments separately. If there are other parameters behind - the redirect URL, this makes it unnecessary to cut them off - by additionally using a +redirect{} pcrs command. - Initial patch submitted by Jamie Zawinski in #3429848. - - When loading action sections, verify that the referenced filters - exist. Currently missing filters only result in an error message, - but eventually the severity will be upgraded to fatal. - - Allow to bind to multiple separate addresses. - Patch set submitted by Petr Pisar in #3354485. - - Set socket_error to errno if connecting fails in rfc2553_connect_to(). - Previously rejected direct connections could be incorrectly reported - as DNS issues if Privoxy was compiled with IPv6 support. - - Adjust url_code_map[] so spaces are replaced with %20 instead of '+' - While '+' can be used by client's submitting form data, this is not - actually what Privoxy is using the lookups for. This is more of a - cosmetic issue and doesn't fix any known problems. - - When compiled without FEATURE_FAST_REDIRECTS, do not silently - ignore +fast-redirect{} directives - - Added a workaround for GNU libc's strptime() reporting negative - year values when the parsed year is only specified with two digits. - On affected systems cookies with such a date would not be turned - into session cookies by the +session-cookies-only action. - Reported by Vaeinoe in #3403560 - - Fixed bind failures with certain GNU libc versions if no non-loopback - IP address has been configured on the system. This is mainly an issue - if the system is using DHCP and Privoxy is started before the network - is completely configured. - Reported by Raphael Marichez in #3349356. - Additional insight from Petr Pisar. - - Privoxy log messages now use the ISO 8601 date format %Y-%m-%d. - It's only slightly longer than the old format, but contains - the full date including the year and allows sorting by date - (when grepping in multiple log files) without hassle. - - In get_last_url(), do not bother trying to decode URLs that do - not contain at least one '%' sign. It reduces the log noise and - a number of unnecessary memory allocations. - - In case of SOCKS5 failures, dump the socks response in the log message. - - Simplify the signal setup in main(). - - Streamline socks5_connect() slightly. - - In socks5_connect(), require a complete socks response from the server. - Previously Privoxy didn't care how much data the server response - contained as long as the first two bytes contained the expected - values. While at it, shrink the buffer size so Privoxy can't read - more than a whole socks response. - - In chat(), do not bother to generate a client request in case of - direct CONNECT requests. It will not be used anyway. - - Reduce server_last_modified()'s stack size. - - Shorten get_http_time() by using strftime(). - - Constify the known_http_methods pointers in unknown_method(). - - Constify the time_formats pointers in parse_header_time(). - - Constify the formerly_valid_actions pointers in action_used_to_be_valid(). - - Introduce a GNUMakefile MAN_PAGE variable that defaults to privoxy.1. - The Debian package uses section 8 for the man page and this - should simplify the patch. - - Deduplicate the INADDR_NONE definition for Solaris by moving it to jbsockets.h - - In block_url(), ditch the obsolete workaround for ancient Netscape versions - that supposedly couldn't properly deal with status code 403. - - Remove a useless NULL pointer check in load_trustfile(). - - Remove two useless NULL pointer checks in load_one_re_filterfile(). - - Change url_code_map[] from an array of pointers to an array of arrays - It removes an unnecessary layer of indirection and on 64bit system reduces - the size of the binary a bit. - - Fix various typos. Fixes taken from Debian's 29_typos.dpatch by Roland Rosenfeld. - - Add a dok-tidy GNUMakefile target to clean up the messy HTML - generated by the other dok targets. - - GNUisms in the GNUMakefile have been removed. - - Change the HTTP version in static responses to 1.1 - - Synced config.sub and config.guess with upstream - 2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5. - - Add a dedicated function to parse the values of toggles. Reduces duplicated - code in load_config() and provides better error handling. Invalid or missing - toggle values are now a fatal error instead of being silently ignored. - - Terminate HTML lines in static error messages with \n instead of \r\n. - - Simplify cgi_error_unknown() a bit. - - In LogPutString(), don't bother looking at pszText when not - actually logging anything. - - Change ssplit()'s fourth parameter from int to size_t. - Fixes a clang complaint. - - Add a warning that the statistics currently can't be trusted. - Mention Privoxy-Log-Parser's --statistics option as - an alternative for the time being. - - In rfc2553_connect_to(), start setting cgi->error_message on error. - - Change the expected status code returned for http://p.p/die depending - on whether or not FEATURE_GRACEFUL_TERMINATION is available. - - In cgi_die(), mark the client connection for closing. - If the client will fetch the style sheet through another connection - it gets the main thread out of the accept() state and should thus - trigger the actual shutdown. - - Add a proper CGI message for cgi_die(). - - Don't enforce a logical line length limit in read_config_line(). - - Slightly refactor server_last_modified() to remove useless gmtime*() calls. - - In get_content_type(), also recognize '.jpeg' as JPEG extension. - - Add '.png' to the list of recognized file extensions in get_content_type(). - - In block_url(), consistently use the block reason "Request blocked by Privoxy" - In two places the reason was "Request for blocked URL" which hides the - fact that the request got blocked by Privoxy and isn't necessarily - correct as the block may be due to tags. - - In listen_loop(), reload the configuration files after accepting - a new connection instead of before. - Previously the first connection that arrived after a configuration - change would still be handled with the old configuration. - - In chat()'s receive-data loop, skip a client socket check if - the socket will be written to right away anyway. This can - increase the transfer speed for unfiltered content on fast - network connections. - - The socket timeout is used for SOCKS negotiations as well which - previously couldn't timeout. - - Don't keep the client connection alive if any configuration file - changed since the time the connection came in. This is closer to - Privoxy's behaviour before keep-alive support for client connection - has been added and also less confusing in general. - - Treat all Content-Type header values containing the pattern - 'script' as a sign of text. Reported by pribog in #3134970. + - 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. + - Improved a couple of error messages. + - Saved memory allocations when using OpenSSL and checking if a + key already exists. + - The configure script will bail out if OpenSSL and mbedTLS are + enabled at the same time. + - Log a message right before exiting gracefully. + - A couple of structures have been rearranged to require slightly + less memory. + - When https inspection is enabled and the certificate is invalid + the error message is now sent with status code 403 instead of 200. + - The Slackware rc script template has been renamed to + slackware/rc.privoxy.in to silence complaints when building + Debian packages. + - 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: - - Moved the site-specific block pattern section below the one for the - generic patterns so for requests that are matched in both, the block - reason for the domain is shown which is usually more useful than showing - the one for the generic pattern. - - Remove -prevent-compression from the fragile alias. It's no longer - used anywhere by default and isn't known to break stuff anyway. - - Add a (disabled) section to block various Facebook tracking URLs. - Reported by Dan Stahlke in #3421764. - - Add a (disabled) section to rewrite and redirect click-tracking - URLs used on news.google.com. - Reported by Dan Stahlke in #3421755. - - Unblock linuxcounter.net/. - Reported by Dan Stahlke in #3422612. - - Block 'www91.intel.com/' which is used by Omniture. - Reported by Adam Piggott in #3167370. - - Disable the handle-as-empty-doc-returns-ok option and mark it as deprecated. - Reminded by tceverling in #2790091. - - Add ".ivwbox.de/" to the "Cross-site user tracking" section. - Reported by Nettozahler in #3172525. - - Unblock and fast-redirect ".awin1.com/.*=http://". - Reported by Adam Piggott in #3170921. - - Block "b.collective-media.net/". - - Widen the Debian popcon exception to "qa.debian.org/popcon". - Seen in Debian's 05_default_action.dpatch by Roland Rosenfeld. - - Block ".gemius.pl/" which only seems to be used for user tracking. - Reported by johnd16 in #3002731. Additional input from Lee and movax. - - Disable banners-by-size filters for '.thinkgeek.com/'. - The filter only seems to catch pictures of the inventory. - - Block requests for 'go.idmnet.bbelements.com/please/showit/'. - Reported by kacperdominik in #3372959. - - Unblock adainitiative.org/. - - Add a fast-redirects exception for '.googleusercontent.com/.*=cache'. - - Add a fast-redirects exception for webcache.googleusercontent.com/. - - Unblock http://adassier.wordpress.com/ and http://adassier.files.wordpress.com/. + - 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/. + - Block requests for trc-events.taboola.com/. - Filter file improvements: - - Let the yahoo filter hide '.ads'. - - Let the msn filter hide overlay ads for Facebook 'likes' in search - results and elements with the id 's_notf_div'. They only seem to be - used to advertise site 'enhancements'. - - Let the js-events filter additionally disarm setInterval(). - Suggested by dg1727 in #3423775. - -- Documentation improvements: - - Clarify the effect of compiling Privoxy with zlib support. - Suggested by dg1727 in #3423782. - - Point out that the SourceForge messaging system works like a black - hole and should thus not be used to contact individual developers. - - Mention some of the problems one can experience when not explicitly - configuring an IP addresses as listen address. - - Explicitly mention that hostnames can be used instead of IP addresses - for the listen-address, that only the first address returned will be - used and what happens if the address is invalid. - Requested by Calestyo in #3302213. - -- Log message improvements: - - If only the server connection is kept alive, do not pretend to - wait for a new client request. - - Remove a superfluous log message in forget_connection(). - - In chat(), properly report missing server responses as such - instead of calling them empty. - - In forwarded_connect(), fix a log message nobody should ever see. - - Fix a log message in socks5_connect(), a failed write operation - was logged as failed read operation. - - Let load_one_actions_file() properly complain about a missing - '{' at the beginning of the file. - Simply stating that a line is invalid isn't particularly helpful. - - Do not claim to listen on a socket until Privoxy actually does. - Patch submitted by Petr Pisar #3354485 - - Prevent a duplicated LOG_LEVEL_CLF message when sending out - the "no-server-data" response. - - Also log the client socket when dropping a connection. - - Include the destination host in the 'Request ... marked for - blocking. limit-connect{...} doesn't allow CONNECT ...' message - Patch submitted by Saperski in #3296250. - - Prevent a duplicated log message if none of the resolved IP - addresses were reachable. - - In connect_to(), do not pretend to retry if forwarded-connect-retries - is zero or unset. - - When a specified user or group can't be found, put the name in - single-quotes when logging it. - - In rfc2553_connect_to(), explain getnameinfo() errors better. - - Remove a useless log message in chat(). - - When retrying to connect, also log the maximum number of connection - attempts. - - Rephrase a log message in compile_dynamic_pcrs_job_list(). - Divide the error code and its meaning with a colon. Call the pcrs - job dynamic and not the filter. Filters may contain dynamic and - non-dynamic pcrs jobs at the same time. Only mention the name of - the filter or tagger, but don't claim it's a filter when it could - be a tagger. - - In a fatal error message in load_one_actions_file(), cover both - URL and TAG patterns. - - In pcrs_strerror(), properly report unknown positive error code - values as such. Previously they were handled like 0 (no error). - - In compile_dynamic_pcrs_job_list(), also log the actual error code as - pcrs_strerror() doesn't handle all errors reported by pcre. - - Don't bother trying to continue chatting if the client didn't ask for it. - Reduces log noise a bit. - - Make two fatal error message in load_one_actions_file() more descriptive. - - In cgi_send_user_manual(), log when rejecting a file name due to '/' or '..'. - - In load_file(), log a message if opening a file failed. - The CGI error message alone isn't too helpful. - - In connection_destination_matches(), improve two log messages - to help understand why the destinations don't match. - - Rephrase a log message in serve(). Client request arrival - should be differentiated from closed client connections now. - - In serve(), log if a client connection isn't reused due to a - configuration file change. - - Let mark_server_socket_tainted() always mark the server socket tainted, - just don't talk about it in cases where it has no effect. It doesn't change - Privoxy's behaviour, but makes understanding the log file easier. - -- configure: - - Added a --disable-ipv6-support switch for platforms where support - is detected but doesn't actually work. - - Do not check for the existence of strerror() and memmove() twice - - Remove a useless test for setpgrp(2). Privoxy doesn't need it and - it can cause problems when cross-compiling. - - Rename the --disable-acl-files switch to --disable-acl-support. - Since about 2001, ACL directives are specified in the standard - config file. - - Update the URL of the 'Removing outdated PCRE version after the - next stable release' posting. The old URL stopped working after - one of SF's recent site "optimizations". Reported by Han Liu. - -- Privoxy-Regression-Test: - - Added --shuffle-tests option to increase the chances of detection race conditions. - - Added a --local-test-file option that allows to use Privoxy-Regression-Test without Privoxy. - - Added tests for missing socks4 and socks4a forwarders. - - The --privoxy-address option now works with IPv6 addresses containing brackets, too. - - Perform limited sanity checks for parameters that are supposed to have numerical values. - - Added a --sleep-time option to specify a number of seconds to - sleep between tests, defaults to 0. - - Disable the range-requests tagger for tests that break if it's enabled. - - Log messages use the ISO 8601 date format %Y-%m-%d. - - Fix spelling in two error messages. - - In the --help output, include a list of supported tests and their default levels. - - Adjust the tests to properly deal with FEATURE_TOGGLE being disabled. + - 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. + - 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: - - Perform limited sanity checks for command line parameters that - are supposed to have numerical values. - - Implement a --unbreak-lines-only option to try to revert MUA breakage. - - Accept and highlight: Added header: Content-Encoding: deflate - - Accept and highlight: Compressed content from 29258 to 8630 bytes. - - Accept and highlight: Client request arrived in time on socket 21. - - Highlight: Didn't receive data in time: a.fsdn.com:443 - - Accept log messages with ISO 8601 time stamps, too. + - Highlight a few more messages. + - Add a handler for tagging messages. + - Properly deal with 'Certificate error' crunches + Previously the error description was highlighted as 'host'. + - Log truncated LOG_LEVEL_CLF messages more gracefully + and note that the statistics will be imprecise. + - Fixed perldoc typo. + - Bump version to 0.9.2. + +- Privoxy-Regression-Test: + - Use http://127.0.0.1:8118/ as default Privoxy address + unless http_proxy is set through the environment. + - 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. + - 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. + - Use --proxy-header when using a CGI prefix with https:// + and a "Host:" header. + - Allow '|' in tokens and values to allow tag patterns like + "TAG:^(application|text)/(x-)?javascript$". + - When get_cgi_page_or_else() fails, include the URL of the + requested page in the log message. + - 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. + - Bumped version to 0.7.2 - uagen: - - Bump generated Firefox version to 8.0. - - Only randomize the release date if the new --randomize-release-date - option is enabled. Firefox versions after 4 use a fixed date string - without meaning. + - Update example output. + - Recommend the use of the https-inspection action in the documentation. + - Upgrade a couple of URLs to https://. + - Add ElectroBSD to the list of operating systems. + - Bumped generated Firefox version to 78 (ESR). + - Bumped version to 1.2.2. + + - User documentation: + - 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. + - Describe how to check if Privoxy has been built with + FEATURE_HTTPS_INSPECTION. + - 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. + +- Developer manual: + - 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. + - 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. + - Add the -s flag to the suggested 'git tag' command. We prefer signed tags. + - Mention that merges into 'master' should be avoided. + - Add git commands that should result in a merge-free history. + - Mention Privoxy-Regression-Test. + - Add a section id to reduce link churn. + - Recommend the dok-tidy target when building docs for the webserver. + - Add another plug for the privoxy-devel mailing list. + - Let the intro link the copyright section in the user manual instead + of giving an incomplete summary of the license status. + - Clarify that the webserver target uploads to the SourceForge webserver. + - Mark the documentation for the Mac OS X installers as out of date and + change the SCM name back to CVS. + - Fix the location of the installer modules for Mac OS X. + They are not actually available through git (yet). + - 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. + +- 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: + - Import a Privoxy logo for the website. + - Update Tor onion service to HiddenServiceVersion 3. + - Display the "model" photos in a single row and remove placeholder images. + - Regenerate homepage with updated sponsor list. + - Use the '/sponsor' redirect for the link to the sponsor page. + - Git commit messages are sent to the Privoxy-commits mailing list. ----------------------------------------------------------------- About Privoxy: @@ -385,73 +319,70 @@ networks. Privoxy is Free Software and licensed under the GNU GPLv2. -Privoxy is an associated project of Software in the Public Interest (SPI). - -Helping hands and donations are welcome: +Our TODO list is rather long. Helping hands and donations are welcome: - * http://www.privoxy.org/faq/general.html#PARTICIPATE + * https://www.privoxy.org/participate - * http://www.privoxy.org/faq/general.html#DONATE + * https://www.privoxy.org/donate -At present, Privoxy is known to run on Windows(95, 98, ME, 2000, -XP, Vista), GNU/Linux (Ubuntu, RedHat, SuSE, Debian, Fedora, Gentoo and -others), Mac OSX, OS/2, AmigaOS, FreeBSD, NetBSD, OpenBSD, Solaris, and -various other flavors of Unix. +At present, Privoxy is known to run on Windows 95 and later versions +(98, ME, 2000, XP, Vista, Windows 7, Windows 10 etc.), GNU/Linux +(RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and others), +Mac OS X (10.4 and upwards on PPC and Intel processors), Haiku, +DragonFly, ElectroBSD, FreeBSD, NetBSD, OpenBSD, Solaris, +and various other flavors of Unix. In addition to the core features of ad blocking and cookie management, Privoxy provides many supplemental features, that give the end-user more control, more privacy and more freedom: + * Supports "Connection: keep-alive". Outgoing connections can be kept + alive independently from the client. Currently not available on all + platforms. - * Supports "Connection: keep-alive". Outgoing connections can be kept - alive independently from the client. Currently not available on all - platforms. + * Supports IPv6, provided the operating system does so too, + and the configure script detects it. - * Supports IPv6, provided the operating system does so too, - and the configure script detects it. + * Supports tagging which allows to change the behaviour based on client + and server headers. - * Supports tagging which allows to change the behaviour based on client - and server headers. + * Supports https inspection which allows to filter https requests. - * Can be run as an "intercepting" proxy, which obviates the need to - configure browsers individually. + * Can be run as an "intercepting" proxy, which obviates the need to + configure browsers individually. - * Sophisticated actions and filters for manipulating both server and - client headers. + * Sophisticated actions and filters for manipulating both server and + client headers. - * Can be chained with other proxies. + * Can be chained with other proxies. - * Integrated browser based configuration and control utility at - http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based - tracing of rule and filter effects. Remote toggling. + * Integrated browser based configuration and control utility at + http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based + tracing of rule and filter effects. Remote toggling. - * Web page filtering (text replacements, removes banners based on size, - invisible web-bugs and HTML annoyances, etc.) + * Web page filtering (text replacements, removes banners based on size, + invisible "web-bugs" and HTML annoyances, etc.) - * Modularized configuration that allows for standard settings and user - settings to reside in separate files, so that installing updated actions - files won't overwrite individual user settings. + * Modularized configuration that allows for standard settings and user + settings to reside in separate files, so that installing updated actions + files won't overwrite individual user settings. - * Support for Perl Compatible Regular Expressions in the configuration - files, and a more sophisticated and flexible configuration syntax. + * Support for Perl Compatible Regular Expressions in the configuration + files, and a more sophisticated and flexible configuration syntax. - * GIF de-animation. + * GIF de-animation. - * Bypass many click-tracking scripts (avoids script redirection). + * Bypass many click-tracking scripts (avoids script redirection). - * User-customizable HTML templates for most proxy-generated pages (e.g. - "blocked" page). + * User-customizable HTML templates for most proxy-generated pages (e.g. + "blocked" page). - * Auto-detection and re-reading of config file changes. - - * Most features are controllable on a per-site or per-location basis. + * Auto-detection and re-reading of config file changes. + * Most features are controllable on a per-site or per-location basis. -Download location: - http://sourceforge.net/project/showfiles.php?group_id=11118 - -Home Page: - http://www.privoxy.org/ +Home Page: + https://www.privoxy.org/ - - Privoxy Developers + - Privoxy Developers