-<!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.17 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.17 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
-> <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.17</SPAN
-> is a stable release.
- The changes since 3.0.16 stable are:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> Fixed last-chunk-detection for responses where the content was small
- enough to be read with the body, causing Privoxy to wait for the
- end of the content until the server closed the connection.
- Reported by "Karsten" in #3028326.
- </P
-></LI
-><LI
-><P
-> Responses with status code 204 weren't properly detected as body-less
- like RFC2616 mandates. Like the previous bug, this caused Privoxy
- to wait for the end of the content until the server closed the connection.
- Fixes #3022042 and #3025553, reported by a user with no visible name.
- Most likely also fixes a bunch of other AJAX-related problem reports
- that got closed in the past due to insufficient information and lack
- of feedback.
- </P
-></LI
-><LI
-><P
-> Fixed an ACL bug that made it impossible to build a blacklist.
- Usually the ACL directives are used in a whitelist, which worked
- as expected, but blacklisting is still useful for public proxies
- where one only needs to deny known abusers access.
- </P
-></LI
-><LI
-><P
-> Added LOG_LEVEL_RECEIVED to log the not-yet-parsed data read from the
- network. This should make debugging various parsing issues a lot easier.
- </P
-></LI
-><LI
-><P
-> The IPv6 code is enabled by default on Windows versions that support it.
- Patch submitted by oCameLo in #2942729.
- </P
-></LI
-><LI
-><P
-> In mingw32 versions, the user.filter file is reachable through the
- GUI, just like default.filter is. Feature request 3040263.
- </P
-></LI
-><LI
-><P
-> Added the configure option --enable-large-file-support to set a few
- defines that are required by platforms like GNU/Linux to support files
- larger then 2GB. Mainly interesting for users without proper logfile
- management.
- </P
-></LI
-><LI
-><P
-> Logging with "debug 16" no longer stops at the first nul byte which is
- pretty useless. Non-printable characters are replaced with their hex value
- so the result can't span multiple lines making parsing them harder then
- necessary.
- </P
-></LI
-><LI
-><P
-> Privoxy logs when reading an action, filter or trust file.
- </P
-></LI
-><LI
-><P
-> Fixed incorrect regression test markup which caused a test in
- 3.0.16 to fail while Privoxy itself was working correctly.
- While Privoxy accepts hide-referer, too, the action name is actually
- hide-referrer which is also the name used one the final results page,
- where the test expected the alias.
- </P
-></LI
-><LI
-><P
-> CGI interface improvements:
- <P
-></P
-><UL
-><LI
-><P
-> In finish_http_response(), continue to add the 'Connection: close'
- header if the client connection will not be kept alive.
- Anonymously pointed out in #2987454.
- </P
-></LI
-><LI
-><P
-> Apostrophes in block messages no longer cause parse errors
- when the blocked page is viewed with JavaScript enabled.
- Reported by dg1727 in #3062296.
- </P
-></LI
-><LI
-><P
-> Fix a bunch of anchors that used underscores instead of dashes.
- </P
-></LI
-><LI
-><P
-> Allow to keep the client connection alive after crunching the previous request.
- Already opened server connections can be kept alive, too.
- </P
-></LI
-><LI
-><P
-> In cgi_show_url_info(), don't forget to prefix URLs that only contain http:// or https:// in the path.
- Fixes #2975765 reported by Adam Piggott.
- </P
-></LI
-><LI
-><P
-> Show the 404 CGI page if cgi_send_user_manual() is called while
- local user manual delivery is disabled.
- </P
-></LI
-></UL
->
- </P
-></LI
-><LI
-><P
-> Action file improvements:
- <P
-></P
-><UL
-><LI
-><P
-> Enable user.filter by default. Suggested by David White in #3001830.
- </P
-></LI
-><LI
-><P
-> Block .sitestat.com/. Reported by johnd16 in #3002725.
- </P
-></LI
-><LI
-><P
-> Block .atemda.com/. Reported by johnd16 in #3002723.
- </P
-></LI
-><LI
-><P
-> Block js.adlink.net/. Reported by johnd16 in #3002720.
- </P
-></LI
-><LI
-><P
-> Block .analytics.yahoo.com/. Reported by johnd16 in #3002713.
- </P
-></LI
-><LI
-><P
-> Block sb.scorecardresearch.com, too. Reported by dg1727 in #2992652.
- </P
-></LI
-><LI
-><P
-> Fix problems noticed on Yahoo mail and news pages.
- </P
-></LI
-><LI
-><P
-> Remove the too broad yahoo section, only keeping the
- fast-redirects exception as discussed on ijbswa-devel@.
- </P
-></LI
-><LI
-><P
-> Don't block adesklets.sourceforge.net. Reported in #2974204.
- </P
-></LI
-><LI
-><P
-> Block chartbeat ping tracking. Reported in #2975895.
- </P
-></LI
-><LI
-><P
-> Tag CSS and image requests with cautious and medium settings, too.
- </P
-></LI
-><LI
-><P
-> Don't handle view.atdmt.com as image. It's used for click-throughs
- so users should be able to "go there anyway".
- Reported by Adam Piggott in #2975927.
- </P
-></LI
-><LI
-><P
-> Also let the refresh-tags filter remove invalid refresh tags where
- the 'url=' part is missing. Anonymously reported in #2986382.
- While at it, update the description to mention the fact that only
- refresh tags with refresh times above 9 seconds are covered.
- </P
-></LI
-><LI
-><P
-> javascript needs to be blocked with +handle-as-empty-document to
- work around Firefox bug 492459. So move .js blockers from
- +block{Might be a web-bug.} -handle-as-empty-document
- to
- +block{Might be a web-bug.} +handle-as-empty-document
- </P
-></LI
-><LI
-><P
-> ijbswa-Feature Requests-3006719 - Block 160x578 Banners.
- </P
-></LI
-><LI
-><P
-> Block another omniture tracking domain
- </P
-></LI
-><LI
-><P
-> Added a range-requests tagger.
- </P
-></LI
-><LI
-><P
-> Added two sections to get Flickr's Ajax interface working with
- default pre-settings. If you change the configuration to block
- cookies by default, you'll need additional exceptions.
- Reported by Mathias Homann in #3101419 and by Patrick on ijbswa-users@
- </P
-></LI
-></UL
->
- </P
-></LI
-><LI
-><P
-> Documentation improvements:
- <P
-></P
-><UL
-><LI
-><P
-> Explicitly mention how to match all URLs.
- </P
-></LI
-><LI
-><P
-> Consistently recommend socks5 in the Tor FAQ entry and mention
- its advantage compared to socks4a. Reported by David in #2960129.
- </P
-></LI
-><LI
-><P
-> Slightly improve the explanation of why filtering may appear
- slower than it is.
- </P
-></LI
-><LI
-><P
-> Grammar fixes for the ACL section.
- </P
-></LI
-></UL
->
- </P
-></LI
-><LI
-><P
-> Privoxy-Log-Parser improvements:
- <P
-></P
-><UL
-><LI
-><P
-> Also gather statistics for blocked and redirected requests.
- </P
-></LI
-><LI
-><P
-> Provide the percentage of keep-alive offers the client accepted.
- </P
-></LI
-><LI
-><P
-> Add a --url-statistics-threshold option.
- </P
-></LI
-><LI
-><P
-> Also gather statistics for ressources, methods, and HTTP versions
- used by the client.
- </P
-></LI
-><LI
-><P
-> Add a --host-statistics-threshold option to also gather
- statistics about how many request where made per host.
- </P
-></LI
-><LI
-><P
-> Fix a bug in handle_loglevel_header() where a 'scan: ' got lost.
- </P
-></LI
-><LI
-><P
-> Add a --shorten-thread-ids option to replace the thread id with
- a decimal number.
- </P
-></LI
-><LI
-><P
-> Accept and ignore: Looks like we got the last chunk together
- with the server headers. We better stop reading.
- </P
-></LI
-><LI
-><P
-> Accept and ignore: Continue hack in da house.
- </P
-></LI
-><LI
-><P
-> Accept and higlight: Rejecting connection from 10.0.0.2.
- Maximum number of connections reached.
- </P
-></LI
-><LI
-><P
-> Accept and highlight: Loading actions file: /usr/local/etc/privoxy/default.action
- </P
-></LI
-><LI
-><P
-> Accept and highlight: Loading filter file: /usr/local/etc/privoxy/default.filter
- </P
-></LI
-><LI
-><P
-> Accept and highlight: Killed all-caps Host header line: HOST: bestproxydb.com
- </P
-></LI
-><LI
-><P
-> Accept and highlight: Reducing expected bytes to 0. Marking
- the server socket tainted after throwing 4 bytes away.
- </P
-></LI
-><LI
-><P
-> Accept: Merged multiple header lines to: 'X-FORWARDED-PROTO: http X-HOST: 127.0.0.1'
- </P
-></LI
-></UL
->
- </P
-></LI
-><LI
-><P
-> Code cleanups:
- <P
-></P
-><UL
-><LI
-><P
-> Remove the next member from the client_state struct. Only the main
- thread needs access to all client states so give it its own struct.
- </P
-></LI
-><LI
-><P
-> Garbage-collect request_contains_null_bytes().
- </P
-></LI
-><LI
-><P
-> Ditch redundant code in unload_configfile().
- </P
-></LI
-><LI
-><P
-> Ditch LogGetURLUnderCursor() which doesn't seem to be used anywhere.
- </P
-></LI
-><LI
-><P
-> In write_socket(), remove the write-only variable write_len in
- an ifdef __OS2__ block. Spotted by cppcheck.
- </P
-></LI
-><LI
-><P
-> In connect_to(), don't declare the variable 'flags' on OS/2 where
- it isn't used. Spotted by cppcheck.
- </P
-></LI
-><LI
-><P
-> Limit the scope of various variables. Spotted by cppcheck.
- </P
-></LI
-><LI
-><P
-> In add_to_iob(), turn an interestingly looking for loop into a
- boring while loop.
- </P
-></LI
-><LI
-><P
-> Code cleanup in preparation for external filters.
- </P
-></LI
-><LI
-><P
-> In listen_loop(), mention the socket on which we accepted the
- connection, not just the source IP address.
- </P
-></LI
-><LI
-><P
-> In write_socket(), also log the socket we're writing to.
- </P
-></LI
-><LI
-><P
-> In log_error(), assert that escaped characters get logged
- completely or not at all.
- </P
-></LI
-><LI
-><P
-> In log_error(), assert that ival and sval have reasonable values.
- There's no reason not to abort() if they don't.
- </P
-></LI
-><LI
-><P
-> Remove an incorrect cgi_error_unknown() call in a
- cannnot-happen-situation in send_crunch_response().
- </P
-></LI
-><LI
-><P
-> Clean up white-space in http_response definition and
- move the crunch_reason to the beginning.
- </P
-></LI
-><LI
-><P
-> Turn http_response.reason into an enum and rename it
- to http_response.crunch_reason.
- </P
-></LI
-><LI
-><P
-> Silence a 'gcc (Debian 4.3.2-1.1) 4.3.2' warning on i686 GNU/Linux.
- </P
-></LI
-></UL
->
- </P
-></LI
-><LI
-><P
-> GNUmakefile improvements:
- <P
-></P
-><UL
-><LI
-><P
-> Use $(SSH) instead of ssh, so one only needs to specify a username once.
- </P
-></LI
-><LI
-><P
-> Removed references to the action feedback thingy that hasn't been
- working for years.
- </P
-></LI
-><LI
-><P
-> Consistently use shell.sourceforge.net instead of shell.sf.net so
- one doesn't need to check server fingerprints twice.
- </P
-></LI
-><LI
-><P
-> Removed GNUisms in the webserver and webactions targets so they
- work with standard tar.
- </P
-></LI
-></UL
->
- </P
-></LI
-></UL
-></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
-> has been merged into
- the <TT
-CLASS="FILENAME"
->default.action</TT
-> file.
- </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
-></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>
projects / privoxy.git / blobdiff