<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
-
<html>
<head>
- <meta name="generator" content=
- "HTML Tidy for Linux/x86 (vers 7 December 2008), see www.w3.org">
-
<title>What's New in this Release</title>
- <meta name="GENERATOR" content=
- "Modular DocBook HTML Stylesheet Version 1.79">
- <link rel="HOME" title="Privoxy 3.0.18 User Manual" href="index.html">
+ <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.33 User Manual" href="index.html">
<link rel="PREVIOUS" title="Installation" href="installation.html">
- <link rel="NEXT" title="Quickstart to Using Privoxy" href=
- "quickstart.html">
+ <link rel="NEXT" title="Quickstart to Using Privoxy" href="quickstart.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
- <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="STYLESHEET" type="text/css" href="p_doc.css">
- <style type="text/css">
-body {
- background-color: #EEEEEE;
- color: #000000;
- }
- :link { color: #0000FF }
- :visited { color: #840084 }
- :active { color: #0000FF }
- hr.c1 {text-align: left}
- </style>
</head>
-
-<body class="SECT1">
+<body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="NAVHEADER">
- <table summary="Header navigation table" width="100%" border="0"
- cellpadding="0" cellspacing="0">
+ <table summary="Header navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.18 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.33 User Manual</th>
</tr>
-
<tr>
- <td width="10%" align="left" valign="bottom"><a href=
- "installation.html" accesskey="P">Prev</a></td>
-
+ <td width="10%" align="left" valign="bottom"><a href="installation.html" accesskey="P">Prev</a></td>
<td width="80%" align="center" valign="bottom"></td>
-
- <td width="10%" align="right" valign="bottom"><a href=
- "quickstart.html" accesskey="N">Next</a></td>
+ <td width="10%" align="right" valign="bottom"><a href="quickstart.html" accesskey="N">Next</a></td>
</tr>
</table>
- <hr class="c1" width="100%">
+ <hr align="left" width="100%">
</div>
-
<div class="SECT1">
- <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this
- Release</a></h1>
-
- <p><span class="APPLICATION">Privoxy 3.0.18</span> is a stable release.
- The changes since 3.0.17 stable are:</p>
-
+ <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this Release</a></h1>
+ <p><span class="APPLICATION">Privoxy 3.0.33</span> fixes an XSS issue and multiple DoS issues and a couple of other
+ bugs. The issues also affect earlier Privoxy releases. <span class="APPLICATION">Privoxy 3.0.33</span> also comes
+ with a couple of general improvements an new features.</p>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.33</span> stable:</p>
<ul>
<li>
- <p>Bug fixes:</p>
-
+ <p>Security/Reliability:</p>
<ul>
<li>
- <p>If the 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.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>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.</p>
+ <p>cgi_error_no_template(): Encode the template name to prevent XSS (cross-side scripting) when Privoxy is
+ configured to servce the user-manual itself. Commit 0e668e9409c. OVE-20211102-0001. CVE-2021-44543.
+ Reported by: Artem Ivanov</p>
</li>
-
<li>
- <p>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.</p>
+ <p>get_url_spec_param(): Free memory of compiled pattern spec before bailing. Reported by Joshua Rogers
+ (Opera) who also provided the fix. Commit 652b4b7cb0. OVE-20211201-0003. CVE-2021-44540.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>process_encrypted_request_headers(): Free header memory when failing to get the request destination.
+ Reported by Joshua Rogers (Opera) who also provided the fix. Commit 0509c58045. OVE-20211201-0002.
+ CVE-2021-44541.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>send_http_request(): Prevent memory leaks when handling errors Reported by Joshua Rogers (Opera) who
+ also provided the fix. Commit c48d1d6d08. OVE-20211201-0001. CVE-2021-44542.</p>
</li>
-
+ </ul>
+ </li>
+ <li>
+ <p>Bug fixes:</p>
+ <ul>
<li>
- <p>If forwarded-connect-retries is set, only retry if Privoxy is
- actually forwarding the request. Previously direct connections
- would be retried as well.</p>
+ <p>handle_established_connection(): Skip the poll()/select() calls if TLS data is pending on the server
+ socket. The TLS library may have already consumed all the data from the server response in which case
+ poll() and select() will not detect that data is available to be read. Fixes SF bug #926 reported by Wen
+ Yue.</p>
</li>
-
<li>
- <p>Fixed a small memory leak when retrying connections with IPv6
- support enabled.</p>
+ <p>continue_https_chat(): Update csp->server_connection.request_sent after sending the request to make
+ sure the latency is calculated correctly. Previously https connections were not reused after timeout
+ seconds after the first request made on the connection.</p>
</li>
-
<li>
- <p>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).</p>
+ <p>free_pattern_spec(): Don't try to free an invalid pointer when unloading an action file with a TAG
+ pattern while Privoxy has been compiled without FEATURE_PCRE_HOST_PATTERNS. Closes: SF patch request #147.
+ Patch by Maxim Antonov.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Adjust build_request_line() to create a CONNECT request line when https-inspecting and forwarding to a
+ HTTP proxy. Fixes SF bug #925 reported by Wen Yue.</p>
</li>
-
<li>
- <p>In html_code_map[], use a numeric character reference instead
- of ' which wasn't standardized before XHTML 1.0.</p>
+ <p>load_config(): Add a space that was missing in a log message.</p>
</li>
-
<li>
- <p>Fix an invalid free when compiled with
- FEATURE_GRACEFUL_TERMINATION and shut down through
- http://config.privoxy.org/die</p>
+ <p>read_http_request_body(): Fix two error messages that used an incorrect variable.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>If the the response is chunk-encoded, ignore the Content-Length header sent by the server. Allows to
+ load https://redmine.lighttpd.net/ with filtering enabled.</p>
</li>
</ul>
</li>
-
<li>
<p>General improvements:</p>
-
<ul>
<li>
- <p>Privoxy can (re)compress buffered content before delivering it
- to the client. Disabled by default as most users wouldn't benefit
- from it.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>Allow to bind to multiple separate addresses. Patch set
- submitted by Petr Pisar in #3354485.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>When compiled without FEATURE_FAST_REDIRECTS, do not silently
- ignore +fast-redirect{} directives</p>
- </li>
-
- <li>
- <p>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</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>In case of SOCKS5 failures, dump the socks response in the log
- message.</p>
- </li>
-
- <li>
- <p>Simplify the signal setup in main()</p>
- </li>
-
- <li>
- <p>Streamline socks5_connect() slightly</p>
+ <p>Allow to edit the add-header action through the CGI editor by generalizing the code that got added with
+ the suppress-tag action. Closes SF patch request #146. Patch by Maxim Antonov.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Add a CGI handler for /wpad.dat that returns a Proxy Auto-Configuration (PAC) file. Among other things,
+ it can be used to instruct clients through DHCP to use Privoxy as proxy. For example with the dnsmasq
+ option: dhcp-option=252,http://config.privoxy.org/wpad.dat Initial patch by Richard Schneidt.</p>
</li>
-
<li>
- <p>In chat(), do not bother to generate a client request in case
- of direct CONNECT requests. It will not be used anyway.</p>
+ <p>Don't log the applied actions in process_encrypted_request() Log them in continue_https_chat() instead
+ to mirror chat(). Prevents the applied actions from getting logged twice for the first request on an
+ https-inspected connection.</p>
</li>
-
<li>
- <p>Reduce server_last_modified()'s stack size.</p>
+ <p>OpenSSL generate_host_certificate(): Use config.privoxy.org as Common Name Org and Org Unit if the real
+ host name is too long to get accepted by OpenSSL. Clients should only care about the Subject Alternative
+ Name anyway and we can continue to use the real host name for it. Reported by Miles Wen on
+ privoxy-users@.</p>
</li>
-
<li>
- <p>Shorten get_http_time() by using strftime().</p>
+ <p>Establish the TLS connection with the client earlier and decide how to route the request afterwards.
+ This allows to change the forwarding settings based on information from the https-inspected request, for
+ example the path.</p>
</li>
-
<li>
- <p>Constify the known_http_methods pointers in
- unknown_method().</p>
+ <p>listen_loop(): When shutting down gracefully, close listening ports before waiting for the threads to
+ exit. Allows to start a second Privoxy with the same config file while the first Privoxy is still
+ running.</p>
</li>
-
<li>
- <p>Constify the time_formats pointers in parse_header_time().</p>
+ <p>serve(): Close the client socket as well if the server socket for an inspected connection has been
+ closed. Privoxy currently can't establish a new server connection when the client socket is reused and
+ would drop the connection in continue_https_chat() anyway.</p>
</li>
-
<li>
- <p>Constify the formerly_valid_actions pointers in
- action_used_to_be_valid().</p>
+ <p>Don't disable redirect checkers in redirect_url(). Disable them in handle_established_connection()
+ instead. Doing it in redirect_url() prevented the +redirect{} and +fast-redirects{} actions from being
+ logged with LOG_LEVEL_ACTIONS.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>handle_established_connection(): Slightly improve a comment.</p>
</li>
-
<li>
- <p>Deduplicate the INADDR_NONE definition for Solaris by moving
- it to jbsockets.h</p>
+ <p>handle_established_connection(): Fix a comment.</p>
</li>
-
<li>
- <p>In block_url(), ditch the obsolete workaround for ancient
- Netscape versions that supposedly couldn't properly deal with
- status code 403.</p>
+ <p>socks5_connect(): Fix indentation.</p>
</li>
-
<li>
- <p>Remove a useless NULL pointer check in load_trustfile().</p>
+ <p>handle_established_connection(): Improve an error message.</p>
</li>
-
<li>
- <p>Remove two useless NULL pointer checks in
- load_one_re_filterfile().</p>
+ <p>create_pattern_spec(): Fix ifdef indentation.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Fix comment typos.</p>
</li>
-
<li>
- <p>Fix various typos. Fixes taken from Debian's 29_typos.dpatch
- by Roland Rosenfeld.</p>
+ <p>process_encrypted_request(): Improve a log message. The function only processes request headers and
+ there may still be unread request body data left to process.</p>
</li>
-
<li>
- <p>Add a dok-tidy GNUMakefile target to clean up the messy HTML
- generated by the other dok targets.</p>
+ <p>chat(): Log the applied actions before deciding how to forward the request.</p>
</li>
-
<li>
- <p>GNUisms in the GNUMakefile have been removed.</p>
+ <p>parse_time_header(): Silence a coverity complaint when building without assertions.</p>
</li>
-
<li>
- <p>Change the HTTP version in static responses to 1.1</p>
+ <p>receive_encrypted_request_headers(): Improve a log message.</p>
</li>
-
<li>
- <p>Synced config.sub and config.guess with upstream
- 2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5.</p>
+ <p>mbedTLS get_ciphersuites_from_string(): Use strlcpy() instead of strncpy(). Previously the terminating
+ NUL wasn't copied which resulted in a compiler warning. This didn't cause actual problems as the target
+ buffer was initialized by zalloc_or_die() so the last byte of the target buffer was NUL already. Actually
+ copying the terminating NUL seems clearer, though.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Remove compiler warnings. "log_error(LOG_LEVEL_FATAL, ..." doesn't return but apparently the compiler
+ doesn't know that. Get rid of several "this statement may fall through [-Wimplicit-fallthrough=]"
+ warnings.</p>
</li>
-
<li>
- <p>Terminate HTML lines in static error messages with \n instead
- of \r\n.</p>
+ <p>Store the PEM certificate in a dynamically allocated buffer when https-inspecting. Should prevent errors
+ like: 2021-03-16 22:36:19.148 7f47bbfff700 Error: X509 PEM cert len 16694 is larger than buffer len 16383
+ As a bonus it should slightly reduce the memory usage as most certificates are smaller than the previously
+ used fixed buffer. Reported by: Wen Yue</p>
</li>
-
<li>
- <p>Simplify cgi_error_unknown() a bit.</p>
+ <p>OpenSSL generate_host_certificate(): Fix two error messsages.</p>
</li>
-
<li>
- <p>In LogPutString(), don't bother looking at pszText when not
- actually logging anything.</p>
+ <p>Improve description of handle_established_connection()</p>
</li>
-
<li>
- <p>Change ssplit()'s fourth parameter from int to size_t. Fixes a
- clang complaint.</p>
+ <p>OpenSSL ssl_store_cert(): Translate EVP_PKEY_EC to a string.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>OpenSSL ssl_store_cert(): Remove pointless variable initialization.</p>
</li>
-
<li>
- <p>In rfc2553_connect_to(), start setting cgi->error_message
- on error</p>
+ <p>OpenSSL ssl_store_cert(): Initialize pointer with NULL instead of 0.</p>
</li>
-
- <li>
- <p>Change the expected status code returned for http://p.p/die
- depending on whether or not FEATURE_GRACEFUL_TERMINATION is
- available.</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>Add a proper CGI message for cgi_die().</p>
- </li>
-
- <li>
- <p>Don't enforce a logical line length limit in
- read_config_line()</p>
- </li>
-
- <li>
- <p>Slightly refactor server_last_modified() to remove useless
- gmtime*() calls</p>
- </li>
-
+ </ul>
+ </li>
+ <li>
+ <p>Action file improvements:</p>
+ <ul>
<li>
- <p>In get_content_type(), also recognize '.jpeg' as JPEG
- extension</p>
+ <p>Disable fast-redirects for .microsoftonline.com/.</p>
</li>
-
<li>
- <p>Add '.png' to the list of recognized file extensions in
- get_content_type()</p>
+ <p>Disable fast-redirects for idp.springer.com/.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Disable fast-redirects for .zeit.de/zustimmung.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Unblock adv-archiv.dfn-cert.de/.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Block requests to eu-tlp01.kameleoon.eu/.</p>
</li>
-
<li>
- <p>The socket timeout is used for SOCKS negotiations as well
- which previously couldn't timeout.</p>
+ <p>Block requests to fpa-events.arstechnica.com/.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Unblock nlnet.nl/.</p>
</li>
-
<li>
- <p>Treat all Content-Type header values containing the pattern
- 'script' as a sign of text. Reported by pribog in #3134970.</p>
+ <p>Unblock adguard.com/.</p>
</li>
</ul>
</li>
-
<li>
- <p>Action file improvements:</p>
-
+ <p>Privoxy-Log-Parser:</p>
<ul>
<li>
- <p>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.</p>
- </li>
-
- <li>
- <p>Remove -prevent-compression from the fragile alias It's no
- longer used anywhere by default and isn't known to break stuff
- anyway.</p>
- </li>
-
- <li>
- <p>Add a (disabled) section to block various Facebook tracking
- URLs Reported by Dan Stahlke in #3421764.</p>
- </li>
-
- <li>
- <p>Add a (disabled) section to rewrite and redirect
- click-tracking URLs used on news.google.com Reported by Dan
- Stahlke in #3421755.</p>
- </li>
-
- <li>
- <p>Unblock linuxcounter.net/ Reported by Dan Stahlke in
- #3422612.</p>
- </li>
-
- <li>
- <p>Block 'www91.intel.com/' which is used by Omniture. Reported
- by Adam Piggott in #3167370.</p>
+ <p>Highlight 'Socket timeout 3 reached: http://127.0.0.1:20000/no-filter/chunked-content/36'.</p>
</li>
-
<li>
- <p>Disable the handle-as-empty-doc-returns-ok option and mark it
- as deprecated. Reminded by tceverling in #2790091.</p>
+ <p>Improve documentation for inactivity-detection mode.</p>
</li>
-
<li>
- <p>Add ".ivwbox.de/" to the "Cross-site user tracking" section.
- Reported by Nettozahler in #3172525.</p>
+ <p>Detect date changes when looking for inactivity.</p>
</li>
-
<li>
- <p>Unblock and fast-redirect ".awin1.com/.*=http://" Reported by
- Adam Piggott in #3170921.</p>
+ <p>Add a --passed-request-statistics-threshold option that can be set to get statistics for requests that
+ were passed.</p>
</li>
-
<li>
- <p>Block "b.collective-media.net/".</p>
+ <p>Add a "inactivity detection" mode which can be useful for debugging purposes.</p>
</li>
-
<li>
- <p>Widen the Debian popcon exception to "qa.debian.org/popcon".
- Seen in Debian's 05_default_action.dpatch by Roland
- Rosenfeld.</p>
+ <p>Bump version to 0.9.4.</p>
</li>
-
<li>
- <p>Block ".gemius.pl/" which only seems to be used for user
- tracking. Reported by johnd16 in #3002731. Additional input from
- Lee and movax.</p>
+ <p>Only run print_intro() and print_outro() when syntax highlighting.</p>
</li>
-
<li>
- <p>Disable banners-by-size filters for '.thinkgeek.com/' The
- filter only seems to catch pictures of the inventory.</p>
+ <p>Rephrase a sentence in the documentation.</p>
</li>
-
<li>
- <p>Block requests for 'go.idmnet.bbelements.com/please/showit/'
- Reported by kacperdominik in #3372959.</p>
+ <p>Highlight 'Client socket 7 is no longer usable. The server socket has been closed.'.</p>
</li>
-
<li>
- <p>Unblock adainitiative.org/</p>
+ <p>Clarify --statistics output by explicitly mentioning that the status codes sent by the server may differ
+ from the ones in "debug 512" messages.</p>
</li>
-
<li>
- <p>Add a fast-redirects exception for
- '.googleusercontent.com/.*=cache'</p>
+ <p>Fix typo in the --statistics output.</p>
</li>
-
<li>
- <p>Add a fast-redirects exception for
- webcache.googleusercontent.com/</p>
+ <p>Remove an unused variable.</p>
</li>
-
<li>
- <p>Unblock http://adassier.wordpress.com/ and
- http://adassier.files.wordpress.com/</p>
+ <p>Highlight 'The peer notified us that the connection on socket 11 is going to be closed'.</p>
</li>
</ul>
</li>
-
<li>
- <p>Filter file improvements:</p>
-
+ <p>Privoxy-Regression-Test:</p>
<ul>
<li>
- <p>Let the yahoo filter hide '.ads'</p>
- </li>
-
- <li>
- <p>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'.</p>
- </li>
-
- <li>
- <p>Let the js-events filter additionally disarm setInterval()
- Suggested by dg1727 in #3423775.</p>
+ <p>Remove duplicated word in a comment.</p>
</li>
</ul>
</li>
-
<li>
- <p>Documentation improvements:</p>
-
+ <p>regression-tests.action:</p>
<ul>
<li>
- <p>Clarify the effect of compiling Privoxy with zlib support
- Suggested by dg1727 in #3423782.</p>
+ <p>Add fetch test for http://p.p/wpad.dat.</p>
</li>
-
<li>
- <p>Point out that the SourceForge messaging system works like a
- black hole and should thus not be used to contact individual
- developers.</p>
+ <p>Bump for-privoxy-version to 3.0.33 which introduced the wpad.dat support.</p>
</li>
-
<li>
- <p>Mention some of the problems one can experience when not
- explicitly configuring an IP addresses as listen address.</p>
+ <p>Add more tests for the '/send-banner' code.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Add test for OVE-20210203-0001.</p>
+ </li>
+ <li>
+ <p>Add a test for CVE-2021-20217.</p>
</li>
</ul>
</li>
-
<li>
- <p>Log message improvements:</p>
-
+ <p>uagen:</p>
<ul>
<li>
- <p>If only the server connection is kept alive, do not pretend to
- wait for a new client request.</p>
- </li>
-
- <li>
- <p>Remove a superfluous log message in forget_connection()</p>
- </li>
-
- <li>
- <p>In chat(), properly report missing server responses as such
- instead of calling them empty</p>
- </li>
-
- <li>
- <p>In forwarded_connect(), fix a log message nobody should ever
- see</p>
- </li>
-
- <li>
- <p>Fix a log message in socks5_connect(), a failed write
- operation was logged as failed read operation</p>
- </li>
-
- <li>
- <p>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.</p>
- </li>
-
- <li>
- <p>Do not claim to listen on a socket until Privoxy actually
- does. Patch submitted by Petr Pisar #3354485</p>
- </li>
-
- <li>
- <p>Prevent a duplicated LOG_LEVEL_CLF message when sending out
- the "no-server-data" response</p>
- </li>
-
- <li>
- <p>Also log the client socket when dropping a connection.</p>
- </li>
-
- <li>
- <p>Include the destination host in the 'Request ... marked for
- blocking. limit-connect{...} doesn't allow CONNECT ...' message
- Patch submitted by Saperski in #3296250.</p>
- </li>
-
- <li>
- <p>Prevent a duplicated log message if none of the resolved IP
- addresses were reachable</p>
- </li>
-
- <li>
- <p>In connect_to(), do not pretend to retry if
- forwarded-connect-retries is zero or unset.</p>
- </li>
-
- <li>
- <p>When a specified user or group can't be found, put the name in
- single-quotes when logging it.</p>
- </li>
-
- <li>
- <p>In rfc2553_connect_to(), explain getnameinfo() errors
- better.</p>
- </li>
-
- <li>
- <p>Remove a useless log message in chat()</p>
+ <p>Bump generated Firefox version to 91 (ESR).</p>
</li>
-
<li>
- <p>When retrying to connect, also log the maximum number of
- connection attempts</p>
+ <p>Bump version to 1.2.3.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Bump copyright.</p>
</li>
-
- <li>
- <p>In a fatal error message in load_one_actions_file(), cover
- both URL and TAG patterns.</p>
- </li>
-
- <li>
- <p>In pcrs_strerror(), properly report unknown positive error
- code values as such. Previously they were handled like 0 (no
- error).</p>
- </li>
-
+ </ul>
+ </li>
+ <li>
+ <p>Build system:</p>
+ <ul>
<li>
- <p>In compile_dynamic_pcrs_job_list(), also log the actual error
- code as pcrs_strerror() doesn't handle all errors reported by
- pcre</p>
+ <p>configure: Bump SOURCE_DATE_EPOCH.</p>
</li>
-
<li>
- <p>Don't bother trying to continue chatting if the client didn't
- ask for it. Reduces log noise a bit.</p>
+ <p>GNUmakefile.in: Fix typo.</p>
</li>
-
<li>
- <p>Make two fatal error message in load_one_actions_file() more
- descriptive</p>
+ <p>configure: Add another warning in case --disable-pthread is used while POSIX threads are available.
+ Various features don't even compile when not using threads.</p>
</li>
-
<li>
- <p>In cgi_send_user_manual(), log when rejecting a file name due
- to '/' or '..'</p>
+ <p>Add configure option to enable MemorySanitizer.</p>
</li>
-
<li>
- <p>In load_file(), log a message if opening a file failed The CGI
- error message alone isn't too helpful.</p>
+ <p>Add configure option to enable UndefinedBehaviorSanitizer.</p>
</li>
-
<li>
- <p>In connection_destination_matches(), improve two log messages
- to help understand why the destinations don't match.</p>
+ <p>Add configure option to enable AddressSanitizer.</p>
</li>
-
<li>
- <p>Rephrase a log message in serve(). Client request arrival
- should be differentiated from closed client connections now.</p>
+ <p>Bump copyright.</p>
</li>
-
<li>
- <p>In serve(), log if a client connection isn't reused due to a
- configuration file change.</p>
+ <p>Add a configure option to disable pcre JIT compilation. While JIT compilation makes filtering faster it
+ can cause false-positive valgrind complaints. As reported by Gwyn Ciesla in SF bug 924 it also can cause
+ problems when the SELinux policy does not grant Privoxy "execmem" privileges.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>configure: Remove obsolete RPM_BASE check.</p>
</li>
</ul>
</li>
-
<li>
- <p>configure:</p>
-
+ <p>Windows build system:</p>
<ul>
<li>
- <p>Added a --disable-ipv6-support switch for platforms where
- support is detected but doesn't actually work.</p>
- </li>
-
- <li>
- <p>Do not check for the existence of strerror() and memmove()
- twice</p>
- </li>
-
- <li>
- <p>Remove a useless test for setpgrp(2). Privoxy doesn't need it
- and it can cause problems when cross-compiling.</p>
+ <p>Update the build script to use mbed tls version 2.6.11.</p>
</li>
-
<li>
- <p>Rename the --disable-acl-files switch to
- --disable-acl-support. Since about 2001, ACL directives are
- specified in the standard config file.</p>
+ <p>Update build script to use the final 8.45 pcre library.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Put all the '--enable-xxx' options in the configure call together.</p>
</li>
</ul>
</li>
-
<li>
- <p>Privoxy-Regression-Test:</p>
-
+ <p>macOS build system:</p>
<ul>
<li>
- <p>Added --shuffle-tests option to increase the chances of
- detection race conditions.</p>
- </li>
-
- <li>
- <p>Added a --local-test-file option that allows to use
- Privoxy-Regression-Test without Privoxy</p>
- </li>
-
- <li>
- <p>Added tests for missing socks4 and socks4a forwarders</p>
- </li>
-
- <li>
- <p>The --privoxy-address option now works with IPv6 addresses
- containing brackets, too</p>
- </li>
-
- <li>
- <p>Perform limited sanity checks for parameters that are supposed
- to have numerical values.</p>
- </li>
-
- <li>
- <p>Added a --sleep-time option to specify a number of seconds to
- sleep between tests, defaults to 0.</p>
- </li>
-
- <li>
- <p>Disable the range-requests tagger for tests that break if it's
- enabled</p>
- </li>
-
- <li>
- <p>Log messages use the ISO 8601 date format %Y-%m-%d.</p>
- </li>
-
- <li>
- <p>Fix spelling in two error messages.</p>
- </li>
-
- <li>
- <p>In the --help output, include a list of supported tests and
- their default levels.</p>
- </li>
-
- <li>
- <p>Adjust the tests to properly deal with FEATURE_TOGGLE being
- disabled.</p>
+ <p>The OSXPackageBuilder repository has been updated and can be used to create macOS packages again.</p>
</li>
</ul>
</li>
-
<li>
- <p>Privoxy-Log-Parser:</p>
-
+ <p>Documentation:</p>
<ul>
<li>
- <p>Perform limited sanity checks for command line parameters that
- are supposed to have numerical values.</p>
+ <p>contacting: Remove obsolete reference to announce.sgml.</p>
</li>
-
<li>
- <p>Implement a --unbreak-lines-only option to try to revert MUA
- breakage.</p>
+ <p>contacting: Request that the browser cache is cleared before producing a log file for submission.</p>
</li>
-
<li>
- <p>Accept and highlight: Added header: Content-Encoding:
- deflate</p>
+ <p>Sponsor FAQ: Note that Privoxy users may follow sponsor links without Referer header set.</p>
</li>
-
<li>
- <p>Accept and highlight: Compressed content from 29258 to 8630
- bytes.</p>
+ <p>newfeatures: Clarify that https inspection also allows to filter https responses.</p>
</li>
-
<li>
- <p>Accept and highlight: Client request arrived in time on socket
- 21.</p>
+ <p>developer-manual: Mention that announce.txt should be updated when doing a release.</p>
</li>
-
<li>
- <p>Highlight: Didn't receive data in time: a.fsdn.com:443</p>
+ <p>config: Explicitly mention that the CGI pages disclosing the ca-password can be blocked and upgrade the
+ disclosure paragraphs to a warning.</p>
</li>
-
<li>
- <p>Accept log messages with ISO 8601 time stamps, too</p>
+ <p>Put all the requested debug options in the config file. Section 11.1 of the Privoxy user manual lists
+ all the debug options that should be enabled when reporting problems or requesting support. Make it easier
+ for users to do the right thing by having all those options present in the config.</p>
+ </li>
+ <li>
+ <p>Update TODO list item #184 to note that WolfSSL support will (hopefully) appear after the 3.0.34
+ release.</p>
</li>
- </ul>
- </li>
-
- <li>
- <p>uagen:</p>
-
- <ul>
<li>
- <p>Bump generated Firefox version to 8.0</p>
+ <p>Update max-client-connections's description. On modern systems other than Windows Privoxy should use
+ poll() in which case the FD_SETSIZE value isn't releveant.</p>
</li>
-
<li>
- <p>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.</p>
+ <p>Add a warning that the socket-timeout does not apply to operations done by TLS libraries.</p>
+ </li>
+ <li>
+ <p>Make documentation slightly less "offensive" for some people by avoiding the word "hell".</p>
</li>
</ul>
</li>
</ul>
-
<div class="SECT2">
- <h2 class="SECT2"><a name="UPGRADERSNOTE" id="UPGRADERSNOTE">3.1. Note
- to Upgraders</a></h2>
-
- <p>A quick list of things to be aware of before upgrading from earlier
- versions of <span class="APPLICATION">Privoxy</span>:</p>
-
+ <h2 class="SECT2"><a name="UPGRADERSNOTE" id="UPGRADERSNOTE">3.1. Note to Upgraders</a></h2>
+ <p>A quick list of things to be aware of before upgrading from earlier versions of <span class=
+ "APPLICATION">Privoxy</span>:</p>
<ul>
<li>
- <p>The recommended way to upgrade <span class=
- "APPLICATION">Privoxy</span> is to backup your old configuration
- files, install the new ones, verify that <span class=
- "APPLICATION">Privoxy</span> is working correctly and finally merge
- back your changes using <span class="APPLICATION">diff</span> and
- maybe <span class="APPLICATION">patch</span>.</p>
-
- <p>There are a number of new features in each <span class=
- "APPLICATION">Privoxy</span> release and most of them have to be
- explicitly enabled in the configuration files. Old configuration
- files obviously don't do that and due to syntax changes using old
- configuration files with a new <span class=
+ <p>The recommended way to upgrade <span class="APPLICATION">Privoxy</span> is to backup your old
+ configuration files, install the new ones, verify that <span class="APPLICATION">Privoxy</span> is working
+ correctly and finally merge back your changes using <span class="APPLICATION">diff</span> and maybe
+ <span class="APPLICATION">patch</span>.</p>
+ <p>There are a number of new features in each <span class="APPLICATION">Privoxy</span> release and most of
+ them have to be explicitly enabled in the configuration files. Old configuration files obviously don't do
+ that and due to syntax changes using old configuration files with a new <span class=
"APPLICATION">Privoxy</span> isn't always possible anyway.</p>
</li>
-
- <li>
- <p>Note that some installers remove earlier versions completely,
- including configuration files, therefore you should really save any
- important configuration files!</p>
- </li>
-
<li>
- <p>On the other hand, other installers don't overwrite existing
- configuration files, thinking you will want to do that
- yourself.</p>
+ <p>Note that some installers remove earlier versions completely, including configuration files, therefore you
+ should really save any important configuration files!</p>
</li>
-
<li>
- <p><tt class="FILENAME">standard.action</tt> has been merged into
- the <tt class="FILENAME">default.action</tt> file.</p>
+ <p>On the other hand, other installers don't overwrite existing configuration files, thinking you will want
+ to do that yourself.</p>
</li>
-
<li>
- <p>In the default configuration only fatal errors are logged now.
- You can change that in the <a href="config.html#DEBUG">debug
- section</a> of the configuration file. You may also want to enable
- more verbose logging until you verified that the new <span class=
- "APPLICATION">Privoxy</span> version is working as expected.</p>
+ <p>In the default configuration only fatal errors are logged now. You can change that in the <a href=
+ "config.html#DEBUG">debug section</a> of the configuration file. You may also want to enable more verbose
+ logging until you verified that the new <span class="APPLICATION">Privoxy</span> version is working as
+ expected.</p>
</li>
-
<li>
- <p>Three other config file settings are now off by default:
- <a href="config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a>,
- <a href=
- "config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>,
- and <a href=
- "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a>. If you
- use or want these, you will need to explicitly enable them, and be
- aware of the security issues involved.</p>
+ <p>Three other config file settings are now off by default: <a href=
+ "config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a>, <a href=
+ "config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>, and <a href=
+ "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a>. If you use or want these, you will need to
+ explicitly enable them, and be aware of the security issues involved.</p>
</li>
</ul>
</div>
</div>
-
<div class="NAVFOOTER">
- <hr class="c1" width="100%">
-
- <table summary="Footer navigation table" width="100%" border="0"
- cellpadding="0" cellspacing="0">
+ <hr align="left" width="100%">
+ <table summary="Footer navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
- <td width="33%" align="left" valign="top"><a href="installation.html"
- accesskey="P">Prev</a></td>
-
- <td width="34%" align="center" valign="top"><a href="index.html"
- accesskey="H">Home</a></td>
-
- <td width="33%" align="right" valign="top"><a href="quickstart.html"
- accesskey="N">Next</a></td>
+ <td width="33%" align="left" valign="top"><a href="installation.html" accesskey="P">Prev</a></td>
+ <td width="34%" align="center" valign="top"><a href="index.html" accesskey="H">Home</a></td>
+ <td width="33%" align="right" valign="top"><a href="quickstart.html" accesskey="N">Next</a></td>
</tr>
-
<tr>
<td width="33%" align="left" valign="top">Installation</td>
-
<td width="34%" align="center" valign="top"> </td>
-
- <td width="33%" align="right" valign="top">Quickstart to Using
- Privoxy</td>
+ <td width="33%" align="right" valign="top">Quickstart to Using Privoxy</td>
</tr>
</table>
</div>