-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><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.10 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="STYLESHEET"
-TYPE="text/css"
-HREF="../p_doc.css"><META
-HTTP-EQUIV="Content-Type"
-CONTENT="text/html;
-charset=ISO-8859-1">
-<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
-</head
-><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"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Privoxy 3.0.10 User Manual</TH
-></TR
-><TR
-><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
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="WHATSNEW"
->3. What's New in this Release</A
-></H1
-><P
-> There are many improvements and new features since <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.8</SPAN
->, the last stable release:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> Added SOCKS5 support (with address resolution done by
- the SOCKS5 server). Patch provided by Eric M. Hopper.
- </P
-></LI
-><LI
-><P
-> The "blocked" CGI pages include a block reason that was
- provided as argument to the last-applying block action.
- </P
-></LI
-><LI
-><P
-> If enable-edit-actions is disabled (the default since 3.0.7 beta)
- the show-status page hides the edit buttons and explains why.
- Previously the user would get the "this feature has been disabled"
- message after using the edit button.
- </P
-></LI
-><LI
-><P
-> Forbidden CONNECT requests are treated like blocks by default.
- The now-pointless treat-forbidden-connects-like-blocks action
- has been removed.
- </P
-></LI
-><LI
-><P
-> Not enabling limit-connect now allows CONNECT requests to all ports.
- In previous versions it would only allow CONNECT requests to port 443.
- Use +limit-connect{443} if you think you need the old default behaviour.
- </P
-></LI
-><LI
-><P
-> The CGI editor gets turned off after three edit requests with invalid
- file modification timestamps. This makes life harder for attackers
- who can leverage browser bugs to send fake Referers and intend to
- brute-force edit URLs.
- </P
-></LI
-><LI
-><P
-> Action settings for multiple patterns in the same section are
- shared in memory. As a result these sections take up less space
- (and are loaded slightly faster). Problem reported by Franz Schwartau.
- </P
-></LI
-><LI
-><P
-> Linear white space in HTTP headers will be normalized to single
- spaces before parsing the header's content, headers split across
- multiple lines get merged first.
- </P
-></LI
-><LI
-><P
-> Host information is gathered outside the main thread so it's less
- likely to delay other incoming connections if the host is misconfigured.
- </P
-></LI
-><LI
-><P
-> New config option "hostname" to use a hostname other than
- the one returned by the operating system. Useful to speed-up responses
- for CGI requests on misconfigured systems. Requested by Max Khon.
- </P
-></LI
-><LI
-><P
-> The CGI editor supports the "disable all filters of this type"
- directives "-client-header-filter", "-server-header-filter",
- "-client-header-tagger" and "-server-header-tagger".
- </P
-></LI
-><LI
-><P
-> Fixed false-positives with the link-by-url filter and URLs that
- contain the pattern "/jump/".
- </P
-></LI
-><LI
-><P
-> The less-download-windows filter no longer messes
- "Content-Type: application/x-shockwave-flash" headers up.
- </P
-></LI
-><LI
-><P
-> In the show-url-info page's "Final results" section active and
- inactive actions are listed separately. Patch provided by Lee.
- </P
-></LI
-><LI
-><P
-> The GNUmakefile supports the DESTDIR variable. Patch for
- the install target submitted by Radoslaw Zielinski.
- </P
-></LI
-><LI
-><P
-> Embedding the content of configuration files in the show-status
- page is significantly faster now. For a largish action file (1 MB)
- a speedup of about 2450 times has been measured. This is mostly
- interesting if you are using large action files or regularly use
- Privoxy-Regression-Test while running Privoxy through Valgrind,
- for stock configuration files it doesn't really matter.
- </P
-></LI
-><LI
-><P
-> If zlib support is unavailable and there are content
- filters active but the prevent-compression action is disabled,
- the show-url-info page includes a warning that compression
- might prevent filtering.
- </P
-></LI
-><LI
-><P
-> The show-url-info page provides an OpenSearch Description that
- allows to access the page through browser search plugins.
- </P
-></LI
-><LI
-><P
-> The obsolete kill-popups action has been removed as the
- PCRS-based popup filters can do the same and are slightly
- less unreliable.
- </P
-></LI
-><LI
-><P
-> The inspect-jpegs action has been removed.
- </P
-></LI
-><LI
-><P
-> The send-wafer and send-vanilla-wafer actions have been removed.
- They weren't particular useful and their behaviour could be emulated
- with add-header anyway.
- </P
-></LI
-><LI
-><P
-> Privoxy-Regression-Test has been significantly improved.
- </P
-></LI
-><LI
-><P
-> Most sections in the default.action file contain tests for
- Privoxy-Regression-Test to verify that they are working as intended.
- </P
-></LI
-><LI
-><P
-> Parts of Privoxy have been refactored to increase maintainability.
- </P
-></LI
-><LI
-><P
-> Building with zlib (if available) is done by default.
- </P
-></LI
-><LI
-><P
-> Ordinary configuration file changes no longer cause program
- termination on OS/2 if the name of the logfile hasn't been
- changed as well. This regression probably crept in with the
- logging improvements in 3.0.7. Reported by Maynard.
- </P
-></LI
-><LI
-><P
-> The img-reorder filter is less likely to mess up JavaScript code in
- img tags. Problem and solution reported by Glenn Washburn in #2014552.
- </P
-></LI
-><LI
-><P
-> The source tar ball now includes Privoxy-Log-Parser,
- a syntax-highlighter for Privoxy logs. Documentation is available
- through perldoc(1), for fancy screenshots see:
- <A
-HREF="http://www.fabiankeil.de/sourcecode/privoxy-log-parser/"
-TARGET="_top"
->http://www.fabiankeil.de/sourcecode/privoxy-log-parser/</A
->.
- </P
-></LI
-></UL
-></P
-><P
-> For a more detailed list of changes please have a look at the ChangeLog.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="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
-><P
-> <P
-></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="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
-></LI
-><LI
-><P
->
- <TT
-CLASS="FILENAME"
->standard.action</TT
-> now only includes the enabled actions.
- Not all actions as before.
- </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
-></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
-></LI
-><LI
-><P
-> The <SPAN
-CLASS="QUOTE"
->"filter-client-headers"</SPAN
-> and
- <SPAN
-CLASS="QUOTE"
->"filter-server-headers"</SPAN
-> actions that were introduced with
- <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.5</SPAN
-> to apply content filters to
- the headers have been removed and replaced with new actions.
- See the <A
-HREF="whatsnew.html"
->What's New section</A
-> above.
- </P
-></LI
-></UL
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><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
-></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
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <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.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="STYLESHEET" type="text/css" href="../p_doc.css">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <link rel="STYLESHEET" type="text/css" href="p_doc.css">
+</head>
+<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">
+ <tr>
+ <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="80%" align="center" valign="bottom"></td>
+ <td width="10%" align="right" valign="bottom"><a href="quickstart.html" accesskey="N">Next</a></td>
+ </tr>
+ </table>
+ <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.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>Security/Reliability:</p>
+ <ul>
+ <li>
+ <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>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>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>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>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>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>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>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>load_config(): Add a space that was missing in a log message.</p>
+ </li>
+ <li>
+ <p>read_http_request_body(): Fix two error messages that used an incorrect variable.</p>
+ </li>
+ <li>
+ <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>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>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>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>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>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>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>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>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>handle_established_connection(): Slightly improve a comment.</p>
+ </li>
+ <li>
+ <p>handle_established_connection(): Fix a comment.</p>
+ </li>
+ <li>
+ <p>socks5_connect(): Fix indentation.</p>
+ </li>
+ <li>
+ <p>handle_established_connection(): Improve an error message.</p>
+ </li>
+ <li>
+ <p>create_pattern_spec(): Fix ifdef indentation.</p>
+ </li>
+ <li>
+ <p>Fix comment typos.</p>
+ </li>
+ <li>
+ <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>chat(): Log the applied actions before deciding how to forward the request.</p>
+ </li>
+ <li>
+ <p>parse_time_header(): Silence a coverity complaint when building without assertions.</p>
+ </li>
+ <li>
+ <p>receive_encrypted_request_headers(): Improve a log message.</p>
+ </li>
+ <li>
+ <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>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>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>OpenSSL generate_host_certificate(): Fix two error messsages.</p>
+ </li>
+ <li>
+ <p>Improve description of handle_established_connection()</p>
+ </li>
+ <li>
+ <p>OpenSSL ssl_store_cert(): Translate EVP_PKEY_EC to a string.</p>
+ </li>
+ <li>
+ <p>OpenSSL ssl_store_cert(): Remove pointless variable initialization.</p>
+ </li>
+ <li>
+ <p>OpenSSL ssl_store_cert(): Initialize pointer with NULL instead of 0.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Action file improvements:</p>
+ <ul>
+ <li>
+ <p>Disable fast-redirects for .microsoftonline.com/.</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for idp.springer.com/.</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .zeit.de/zustimmung.</p>
+ </li>
+ <li>
+ <p>Unblock adv-archiv.dfn-cert.de/.</p>
+ </li>
+ <li>
+ <p>Block requests to eu-tlp01.kameleoon.eu/.</p>
+ </li>
+ <li>
+ <p>Block requests to fpa-events.arstechnica.com/.</p>
+ </li>
+ <li>
+ <p>Unblock nlnet.nl/.</p>
+ </li>
+ <li>
+ <p>Unblock adguard.com/.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Log-Parser:</p>
+ <ul>
+ <li>
+ <p>Highlight 'Socket timeout 3 reached: http://127.0.0.1:20000/no-filter/chunked-content/36'.</p>
+ </li>
+ <li>
+ <p>Improve documentation for inactivity-detection mode.</p>
+ </li>
+ <li>
+ <p>Detect date changes when looking for inactivity.</p>
+ </li>
+ <li>
+ <p>Add a --passed-request-statistics-threshold option that can be set to get statistics for requests that
+ were passed.</p>
+ </li>
+ <li>
+ <p>Add a "inactivity detection" mode which can be useful for debugging purposes.</p>
+ </li>
+ <li>
+ <p>Bump version to 0.9.4.</p>
+ </li>
+ <li>
+ <p>Only run print_intro() and print_outro() when syntax highlighting.</p>
+ </li>
+ <li>
+ <p>Rephrase a sentence in the documentation.</p>
+ </li>
+ <li>
+ <p>Highlight 'Client socket 7 is no longer usable. The server socket has been closed.'.</p>
+ </li>
+ <li>
+ <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>Fix typo in the --statistics output.</p>
+ </li>
+ <li>
+ <p>Remove an unused variable.</p>
+ </li>
+ <li>
+ <p>Highlight 'The peer notified us that the connection on socket 11 is going to be closed'.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Regression-Test:</p>
+ <ul>
+ <li>
+ <p>Remove duplicated word in a comment.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>regression-tests.action:</p>
+ <ul>
+ <li>
+ <p>Add fetch test for http://p.p/wpad.dat.</p>
+ </li>
+ <li>
+ <p>Bump for-privoxy-version to 3.0.33 which introduced the wpad.dat support.</p>
+ </li>
+ <li>
+ <p>Add more tests for the '/send-banner' code.</p>
+ </li>
+ <li>
+ <p>Add test for OVE-20210203-0001.</p>
+ </li>
+ <li>
+ <p>Add a test for CVE-2021-20217.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>uagen:</p>
+ <ul>
+ <li>
+ <p>Bump generated Firefox version to 91 (ESR).</p>
+ </li>
+ <li>
+ <p>Bump version to 1.2.3.</p>
+ </li>
+ <li>
+ <p>Bump copyright.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Build system:</p>
+ <ul>
+ <li>
+ <p>configure: Bump SOURCE_DATE_EPOCH.</p>
+ </li>
+ <li>
+ <p>GNUmakefile.in: Fix typo.</p>
+ </li>
+ <li>
+ <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>Add configure option to enable MemorySanitizer.</p>
+ </li>
+ <li>
+ <p>Add configure option to enable UndefinedBehaviorSanitizer.</p>
+ </li>
+ <li>
+ <p>Add configure option to enable AddressSanitizer.</p>
+ </li>
+ <li>
+ <p>Bump copyright.</p>
+ </li>
+ <li>
+ <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>configure: Remove obsolete RPM_BASE check.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Windows build system:</p>
+ <ul>
+ <li>
+ <p>Update the build script to use mbed tls version 2.6.11.</p>
+ </li>
+ <li>
+ <p>Update build script to use the final 8.45 pcre library.</p>
+ </li>
+ <li>
+ <p>Put all the '--enable-xxx' options in the configure call together.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>macOS build system:</p>
+ <ul>
+ <li>
+ <p>The OSXPackageBuilder repository has been updated and can be used to create macOS packages again.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Documentation:</p>
+ <ul>
+ <li>
+ <p>contacting: Remove obsolete reference to announce.sgml.</p>
+ </li>
+ <li>
+ <p>contacting: Request that the browser cache is cleared before producing a log file for submission.</p>
+ </li>
+ <li>
+ <p>Sponsor FAQ: Note that Privoxy users may follow sponsor links without Referer header set.</p>
+ </li>
+ <li>
+ <p>newfeatures: Clarify that https inspection also allows to filter https responses.</p>
+ </li>
+ <li>
+ <p>developer-manual: Mention that announce.txt should be updated when doing a release.</p>
+ </li>
+ <li>
+ <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>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>
+ <li>
+ <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>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>
+ <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=
+ "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>
+ </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>
+ </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>
+ </li>
+ </ul>
+ </div>
+ </div>
+ <div class="NAVFOOTER">
+ <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>
+ </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>
+ </tr>
+ </table>
+ </div>
+</body>
+</html>