<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.30 User Manual" href="index.html">
+ <link rel="HOME" title="Privoxy 3.0.35 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">
<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.30 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.35 User Manual</th>
</tr>
<tr>
<td width="10%" align="left" valign="bottom"><a href="installation.html" accesskey="P">Prev</a></td>
</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.30</span> fixes a couple of bugs and introduces a few new features.</p>
- <p>Changes in <span class="APPLICATION">Privoxy 3.0.30</span> stable:</p>
+ <p><span class="APPLICATION">Privoxy 3.0.34</span> fixes a few minor bugs and comes with a couple of general
+ improvements and new features.</p>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.34</span> stable:</p>
<ul>
<li>
<p>Bug fixes:</p>
<ul>
<li>
- <p>Check the actual URL for redirects when https inspecting requests. Previously Privoxy would only check
- the path which resulted in rewrite results being rejected as invalid URLs. Reported by withoutname in
- #1736.</p>
+ <p>Improve the handling of chunk-encoded responses by buffering the data even if filters are disabled and
+ properly keeping track of where the various chunks are supposed to start and end. Previously Privoxy would
+ merely check the last bytes received to see if they looked like the last-chunk. This failed to work if the
+ last-chunk wasn't received in one read and could also result in actual data being misdetected as
+ last-chunk. Should fix: SF support request #1739. Reported by: withoutname.</p>
</li>
<li>
- <p>Let the hide-referrer code tolerate Referer headers with https:// URLs. Previously they would always be
- treated like a changed host.</p>
+ <p>remove_chunked_transfer_coding(): Refuse to de-chunk invalid data Previously the data could get
+ corrupted even further. Now we simply pass the unmodified data to the client.</p>
</li>
<li>
- <p>Use the https headers if the show-request handler is reached through https://. Previously Privoxy would
- use the http headers which may be empty on a reused connection.</p>
+ <p>gif_deanimate(): Tolerate multiple image extensions in a row. This allows to deanimate all the gifs on:
+ https://commons.wikimedia.org/wiki/Category:Animated_smilies Fixes SF bug #795 reported by Celejar.</p>
</li>
<li>
- <p>Make CGI_PREFIX protocol-relative when building with FEATURE_HTTPS_INSPECTION. This unbreaks (at least)
- https://config.privoxy.org/client-tags whose buttons would previously use a http:// URL resulting in
- browser warnings.</p>
+ <p>OpenSSL generate_host_certificate(): Use X509_get_subject_name() instead of X509_get_issuer_name() to
+ get the issuer for generated website certificates so there are no warnings in the browser when using an
+ intermediate CA certificate instead of a self-signed root certificate. Problem reported and patch submitted
+ by Chakib Benziane.</p>
</li>
<li>
- <p>Support using https-inspection and client-header-order at the same time. Previously Privoxy would crash.
- Reported by: Kai Raven</p>
+ <p>can_filter_request_body(): Fix a log message that contained a spurious u.</p>
</li>
<li>
- <p>Properly reject rewrites from http to https as they currently aren't supported. Previously Privoxy would
- wait for the client to establish an encrypted connection which obviously would not happen.</p>
+ <p>handle_established_connection(): Check for pending TLS data from the client before checking if data is
+ available on the connection. The TLS library may have already consumed all the data from the client
+ response in which case poll() and select() will not detect that data is available to be read. Sponsored by:
+ Robert Klemme.</p>
</li>
<li>
- <p>When https inspection is enabled and Privoxy has been compiled with FEATURE_GRACEFUL_TERMINATION (not
- recommended for production builds), the TLS backend resources are free'd later on and only if no active
- connections are left. Prevents crashes when exiting "gracefully" at the wrong time.</p>
+ <p>ssl_send_certificate_error(): Don't crash if there's no certificate information available. This is only
+ relevant when Privoxy is built with wolfSSL 5.0.0 or later (code not yet published). Earlier wolfSSL
+ versions or the other TLS backends don't seem to trigger the crash.</p>
+ </li>
+ <li>
+ <p>socks5_connect(): Add support for target hosts specified as IPv4 address Previously the IP address was
+ sent as domain.</p>
</li>
</ul>
</li>
<p>General improvements:</p>
<ul>
<li>
- <p>Allow to rewrite the request destination for https-inspected requests behind the client's back. The
- documentation already sort of claimed that it was supported by not especially mentioning that it didn't
- work for https-inspected requests. Fixes SF bug #923 reported by withoutname.</p>
- </li>
- <li>
- <p>Add support for filtering client request bodies by using CLIENT-BODY-FILTER filters which can be enabled
- with the client-body-filter action. Patch submitted by Maxim Antonov. Sponsored by: Robert Klemme</p>
- </li>
- <li>
- <p>Add the new action suppress-tag{} which can be used to prevent a tagger from adding a tag. Patch
- submitted by Maxim Antonov. Sponsored by: Robert Klemme</p>
- </li>
- <li>
- <p>Gracefully handle existing website keys without matching certificates. This can happen if Privoxy was
- previously running with an invalid TLS configuration that didn't allow it to create a certificate.</p>
- </li>
- <li>
- <p>Recycle debug bit 4 for Tagging-related messages.</p>
- </li>
- <li>
- <p>Improve the message shown when the client-tags CGI page is requested with no tags configured.</p>
- </li>
- <li>
- <p>Shorten the 'donate' and 'participate' links used by templates using redirects. Currently the redirects
- lead to the FAQ entries but in the future we may want to relocate the content and using redirects makes
- this more convenient.</p>
- </li>
- <li>
- <p>Log an error when a PCRE-HOST-PATTERN is used with FEATURE_PCRE_HOST_PATTERNS disabled. Don't treat this
- a fatal error so the regression tests can be used with and without FEATURE_PCRE_HOST_PATTERNS.</p>
- </li>
- <li>
- <p>The code compiles with older C compilers again.</p>
- </li>
- <li>
- <p>The chdir() return code is checked to fix a compiler warning.</p>
- </li>
- <li>
- <p>The packages feed has been removed from the source tarball. It's usually out of date when the source
- tarball is generated for the release.</p>
- </li>
- <li>
- <p>Fixed harmless compiler warnings from GCC9 with -D_FORTIFY_SOURCE=2.</p>
- </li>
- <li>
- <p>windows: Remove obsolete '$(DEST)/doc/images' target.</p>
- </li>
- <li>
- <p>windows: Install the images referenced in the user manual.</p>
- </li>
- <li>
- <p>Remove obsolete 'gnu_regex.@OBJEXT@' target.</p>
- </li>
- <li>
- <p>When installing from the GNUMAkefile, don't create an 'images' directory which is no longer used. The
- images were relocated to the user-manual directory years ago.</p>
- </li>
- <li>
- <p>Add new FEATURES to the show-status page and resort list.</p>
+ <p>Add a client-body-tagger action which creates tags based on the content of the request body. Sponsored
+ by: Robert Klemme.</p>
</li>
<li>
- <p>Remove unused variable in the OpenSSL-specific code.</p>
+ <p>When client-body filters are enabled, buffer the whole request before opening a connection to the
+ server. Makes it less likely that the server connection times out and we don't open a connection if the
+ buffering fails anyway. Sponsored by: Robert Klemme.</p>
</li>
<li>
- <p>Update bug tracker URL in cgi_error_unknown().</p>
+ <p>Add periods to a couple of log messages.</p>
</li>
<li>
- <p>Saved a couple of memory allocations when sorting client headers.</p>
+ <p>accept_connection(): Add missing space to a log message.</p>
</li>
<li>
- <p>Improved a couple of error messages.</p>
+ <p>Initialize ca-related defaults with strdup_or_die() so errors aren't silently ignored.</p>
</li>
<li>
- <p>Saved memory allocations when using OpenSSL and checking if a key already exists.</p>
+ <p>make_path: Use malloc_or_die() in cases where allocation errors were already fatal anyway.</p>
</li>
<li>
- <p>The configure script will bail out if OpenSSL and mbedTLS are enabled at the same time.</p>
+ <p>handle_established_connection(): Improve an error message slightly.</p>
</li>
<li>
- <p>Log a message right before exiting gracefully.</p>
+ <p>receive_client_request(): Reject https URLs without CONNECT request.</p>
</li>
<li>
- <p>A couple of structures have been rearranged to require slightly less memory.</p>
+ <p>Include all requests in the statistics if mutexes are available. Previously in case of reused
+ connections only the last request got counted. The statistics still aren't perfect but it's an
+ improvement.</p>
</li>
<li>
- <p>When https inspection is enabled and the certificate is invalid the error message is now sent with
- status code 403 instead of 200.</p>
+ <p>Add read_socks_reply() and start using it in socks5_connect() to apply the socket timeout more
+ consistently.</p>
</li>
<li>
- <p>The Slackware rc script template has been renamed to slackware/rc.privoxy.in to silence complaints when
- building Debian packages.</p>
+ <p>socks5_connect(): Deal with domain names in the socks reply</p>
</li>
<li>
- <p>When building with MbedTLS support, mbedtls_md5_ret() is used instead of mbedtls_md5() which is
- deprecated and causes a warning on Debian GNU/Linux.</p>
+ <p>Add a filter for bundeswehr.de that hides the cookie and privacy info banner.</p>
</li>
</ul>
</li>
<p>Action file improvements:</p>
<ul>
<li>
- <p>Block requests to eu-tlp03.kameleoon.com/.</p>
+ <p>Disable filter{banners-by-size} for .freiheitsfoo.de/.</p>
</li>
<li>
- <p>Unblock metrics.sr.ht/.</p>
+ <p>Disable filter{banners-by-size} for freebsdfoundation.org/.</p>
</li>
<li>
- <p>Disable fast-redirects for .fsf.org/.</p>
+ <p>Disable fast-redirects for consent.youtube.com/.</p>
</li>
<li>
- <p>Disable fast-redirects for .gravater.com/.</p>
+ <p>Block requests to ups.xplosion.de/.</p>
</li>
<li>
- <p>Disable fast-redirects for .ksta.de/.</p>
+ <p>Block requests for elsa.memoinsights.com/t.</p>
</li>
<li>
- <p>Block requests to tag.crsspxl.com/.</p>
+ <p>Fix a typo in a test.</p>
</li>
<li>
- <p>Block requests to analytics.slashdotmedia.com/.</p>
+ <p>Disable fast-redirects for launchpad.net/.</p>
</li>
<li>
- <p>Block requests to ml314.com/.</p>
+ <p>Unblock .eff.org/.</p>
</li>
<li>
- <p>Block requests to .adroll.com/.</p>
+ <p>Stop unblocking .org/.*(image|banner) which appears to be too generous The example URL
+ http://www.gnu.org/graphics/gnu-head-banner.png is already unblocked due to .gnu.org being unblocked.</p>
</li>
<li>
- <p>Block requests to fastlane.rubiconproject.com/.</p>
+ <p>Unblock adfd.org/.</p>
</li>
<li>
- <p>Block requests to api.theadex.com/.</p>
+ <p>Disable filter{banners-by-link} for .eff.org/.</p>
</li>
<li>
- <p>Block requests to ih.adscale.de/.</p>
+ <p>Block requests to odb.outbrain.com/.</p>
</li>
<li>
- <p>Block requests to .s400.meetrics.net/.</p>
+ <p>Disable fast-redirects for .gandi.net/.</p>
</li>
<li>
- <p>Block requests for pp.lp4.io/.</p>
+ <p>Disable fast-redirects{} for .onion/.*/status/.</p>
</li>
<li>
- <p>Block requests for trc-events.taboola.com/.</p>
+ <p>Disable fast-redirects{} for twitter.com/.*/status/.</p>
</li>
- </ul>
- </li>
- <li>
- <p>Filter file improvements:</p>
- <ul>
<li>
- <p>A allow-autocompletion filter has been added which changes autocomplete="off" to "on" on input fields to
- allow autocompletion. Requested by Jamie Zawinski in #370. Filter based on a submission by Aaron
- Linville.</p>
+ <p>Unblock pinkstinks.de/.</p>
</li>
<li>
- <p>Added an imdb filter.</p>
- </li>
- <li>
- <p>Added a sourceforge filter that reduces the amount of ads for proprietary software.</p>
- </li>
- <li>
- <p>Added a github filter that removes the annoying "Sign-Up" banner and the Cookie disclaimer.</p>
- </li>
- <li>
- <p>Removed a duplicated pcrs command from the js-annoyances filter.</p>
- </li>
- <li>
- <p>The crude-parental filter now provides a short reason when blocking, inserts a link to Privoxy's
- webinterface and adds a new line at the end of the generated page.</p>
+ <p>Disable fast-redirects for .hagalil.com/.</p>
</li>
</ul>
</li>
<p>Privoxy-Log-Parser:</p>
<ul>
<li>
- <p>Highlight a few more messages.</p>
- </li>
- <li>
- <p>Add a handler for tagging messages.</p>
- </li>
- <li>
- <p>Properly deal with 'Certificate error' crunches Previously the error description was highlighted as
- 'host'.</p>
- </li>
- <li>
- <p>Log truncated LOG_LEVEL_CLF messages more gracefully and note that the statistics will be imprecise.</p>
- </li>
- <li>
- <p>Fixed perldoc typo.</p>
- </li>
- <li>
- <p>Bump version to 0.9.2.</p>
- </li>
- </ul>
- </li>
- <li>
- <p>Privoxy-Regression-Test:</p>
- <ul>
- <li>
- <p>Use http://127.0.0.1:8118/ as default Privoxy address unless http_proxy is set through the
- environment.</p>
- </li>
- <li>
- <p>Add a --privoxy-cgi-prefix option that specifies the prefix to use when building URLs that are supposed
- to reach Privoxy's CGI interface. If it's not set, http://p.p/ is used, which is supposed to work with the
- default Privoxy configuration. If Privoxy has been built with FEATURE_HTTPS_INSPECTION enabled, and if
- https inspection is activated with the +https-inspection action, this option can be used with
- "https://p.p/" provided the system running Privoxy-Regression-Test has been configured to trust the
- certificate used by Privoxy. Note that there are currently two tests in the official
- regression-tests.action file that are expected to fail when using "https://p.p/" as privoxy-cgi-prefix.</p>
- </li>
- <li>
- <p>Skip the connection-established response in get_status_code() when looking for the status code with a
- CGI prefix that starts with https://. We care about the status code sent by the impersonated web
- server.</p>
- </li>
- <li>
- <p>Use --proxy-header when using a CGI prefix with https:// and a "Host:" header.</p>
+ <p>Bump version to 0.9.5.</p>
</li>
<li>
- <p>Allow '|' in tokens and values to allow tag patterns like
- "TAG:^(application|text)/(x-)?javascript$".</p>
+ <p>Highlight more log messages.</p>
</li>
<li>
- <p>When get_cgi_page_or_else() fails, include the URL of the requested page in the log message.</p>
- </li>
- <li>
- <p>Added a --check-bad-ssl option that can be used to verify that Privoxy detects certificate problems when
- accessing the test sites from badssl.com.</p>
- </li>
- <li>
- <p>Bumped version to 0.7.2</p>
+ <p>Highlight the Crunch reason only once. Previously the "crunch reason" could also be highlighted when the
+ URL contained a matching string. The real crunch reason only occurs once per line, so there's no need to
+ continue looking for it after it has been found once. While at it, add a comment with an example log
+ line.</p>
</li>
</ul>
</li>
<p>uagen:</p>
<ul>
<li>
- <p>Update example output.</p>
- </li>
- <li>
- <p>Recommend the use of the https-inspection action in the documentation.</p>
- </li>
- <li>
- <p>Upgrade a couple of URLs to https://.</p>
- </li>
- <li>
- <p>Add ElectroBSD to the list of operating systems.</p>
- </li>
- <li>
- <p>Bumped generated Firefox version to 78 (ESR).</p>
- </li>
- <li>
- <p>Bumped version to 1.2.2.</p>
- </li>
- </ul>
- </li>
- <li>
- <p>User documentation:</p>
- <ul>
- <li>
- <p>Remove reference to 'How to Report Bugs Effectively'. It was only rendered as text without URL in the
- README anyway and there's no indication that users read it ...</p>
- </li>
- <li>
- <p>Let the dok-readme target fix the location embedded into the README file. This used to be done by CVS
- but since the git migration it has to be done through other means.</p>
- </li>
- <li>
- <p>Remove 'experimental' warning for client-specific-tag-related directives. They seem to work reliably and
- there is no obvious reason why we would change the syntax in the near future.</p>
- </li>
- <li>
- <p>Describe how to check if Privoxy has been built with FEATURE_HTTPS_INSPECTION.</p>
- </li>
- <li>
- <p>Add a link to the trusted-cas-file documentation that explains how the user can create the file
- herself.</p>
- </li>
- <li>
- <p>Don't explicitly mention the license for the code coming from 'Anonymous Coders' and Junkbusters. It's
- obviously licensed under the GNU GPL like the rest of Privoxy or we wouldn't be allowed to distribute
- it.</p>
- </li>
- <li>
- <p>Update the +hide-user-agent example with uagen output.</p>
- </li>
- <li>
- <p>Slightly improve the wording of the ca-key-file documentation.</p>
- </li>
- <li>
- <p>Explicitly mention Windows 10 as supported so search engines and users looking for it can find it.</p>
- </li>
- <li>
- <p>Import a bunch of contributors from the ChangeLog.</p>
- </li>
- <li>
- <p>Remove obsolete doc/gpl.html.</p>
+ <p>Bump version to 1.2.4.</p>
</li>
<li>
- <p>Upgrade a couple of links to https://.</p>
+ <p>Update BROWSER_VERSION and BROWSER_REVISION to 102.0 to match the User-Agent of the current Firefox
+ ESR.</p>
</li>
<li>
- <p>Don't prefer the SourceForge patch tracker over the privoxy-devel mailing list. While at it, link to the
- SourceForge patch tracker.</p>
+ <p>Explicitly document that changing the 'Gecko token' is suspicious.</p>
</li>
<li>
- <p>Mention http-inspection in the 'my browser warns me about unauthenticated content' FAQ entry.</p>
+ <p>Consistently use a lower-case 'c' as copyright symbol.</p>
</li>
<li>
- <p>Simplify the 'Is there is a license or fee?' FAQ entry.</p>
+ <p>Bump copyright.</p>
</li>
<li>
- <p>Add another +redirect{} example.</p>
+ <p>Add 'aarch64' as Linux architecture.</p>
</li>
<li>
- <p>Explicitly mention that interested sponsors should include the link target in their first mail.</p>
+ <p>Add OpenBSD architecture 'arm64'.</p>
</li>
<li>
- <p>Clarify that only Privoxy team members can object to new sponsors and link to the list of current team
- members.</p>
- </li>
- <li>
- <p>Note that sponsor URLs may not contain keyword spam.</p>
- </li>
- <li>
- <p>Garbage collect doc/webserver/images which isn't referenced anymore.</p>
- </li>
- <li>
- <p>Update the method to reach the proxy settings in Firefox.</p>
- </li>
- <li>
- <p>Update proxy_setup.jpg description to refer to Firefox.</p>
- </li>
- <li>
- <p>Regenerate proxy_setup.jpg with a more recent Firefox (78.0).</p>
- </li>
- <li>
- <p>Regenerate files-in-use.jpg without obsolete standard.action with modern colors and a slightly better
- quality.</p>
- </li>
- <li>
- <p>Update URL to the actionsfile tracker.</p>
- </li>
- <li>
- <p>Update a support request URL.</p>
- </li>
- <li>
- <p>Rephrase the 'Can Privoxy run as service' FAQ entry and remove an obsolete paragraph.</p>
- </li>
- <li>
- <p>Let the 'Where can I get updated Actions Files?' entry link to the gitweb version of
- default.action.master.</p>
- </li>
- <li>
- <p>Update a link to the default.action file.</p>
- </li>
- <li>
- <p>Update URLs for trackers and mailing lists.</p>
- </li>
- <li>
- <p>Replace CVS reference with git.</p>
- </li>
- <li>
- <p>Mention regression-tests.action in the config file.</p>
- </li>
- <li>
- <p>Explicitly mention in the config file that access to the CA key should be limited to Privoxy.</p>
- </li>
- <li>
- <p>List more client-specific-tag examples for inspiration.</p>
- </li>
- <li>
- <p>Add additional headers to the client-header-order example.</p>
- </li>
- <li>
- <p>Note that actions aren't updated after rewrites.</p>
- </li>
- <li>
- <p>Explicitly mention that upgrading from http to https with a client-header filter is not supported</p>
- </li>
- <li>
- <p>Note that protocol and host have to be added when rewriting the destination host for https-inspected
- requests.</p>
- </li>
- <li>
- <p>Explicitly mention that the CA key is used to sign certificates.</p>
- </li>
- <li>
- <p>Put openssl command in 'command' tags.</p>
- </li>
- <li>
- <p>The man page has been moved from section 1 to man section 8.</p>
+ <p>Stop using sparc64 as FreeBSD architecture. It hasn't been supported for a while now.</p>
</li>
</ul>
</li>
<li>
- <p>Developer manual:</p>
+ <p>Build system:</p>
<ul>
<li>
- <p>Flesh out the build instructions for Debian.</p>
- </li>
- <li>
- <p>Remove the packaging instructions for RPM-based systems. They don't work and we don't release RPM
- packages anymore anyway.</p>
- </li>
- <li>
- <p>Remove the packaging instructions for Solaris. They don't work and we don't release Solaris packages
- anymore anyway.</p>
- </li>
- <li>
- <p>Update the suggested subject for the announce mails.</p>
- </li>
- <li>
- <p>Update upload instructions. ftp://upload.sourceforge.net is no longer functional.</p>
+ <p>Makefile: Add a 'dok' target that depends on the 'error' target to show the "You are not using GNU make
+ or did nor run configure" message.</p>
</li>
<li>
- <p>Remove a couple of package-dependent upload instructions that don't actually work.</p>
- </li>
- <li>
- <p>Remove 'cd current' that no longer works.</p>
- </li>
- <li>
- <p>Add regression-tests.action to the list of files that should be installed.</p>
- </li>
- <li>
- <p>Stop claiming that there are text versions of the manuals. We stopped building them in 2008
- (9ed36a3c5e6f12).</p>
- </li>
- <li>
- <p>Note that the 'webserver' target creates the link needed for the user-manual.</p>
- </li>
- <li>
- <p>Suggest to use the master branch as reference when creating the ChangeLog so the steps work when the
- current branch differs from master which is likely as the developer manual suggests to use a local branch
- for development.</p>
- </li>
- <li>
- <p>Add the -s flag to the suggested 'git tag' command. We prefer signed tags.</p>
- </li>
- <li>
- <p>Mention that merges into 'master' should be avoided.</p>
- </li>
- <li>
- <p>Add git commands that should result in a merge-free history.</p>
- </li>
- <li>
- <p>Mention Privoxy-Regression-Test.</p>
- </li>
- <li>
- <p>Add a section id to reduce link churn.</p>
- </li>
- <li>
- <p>Recommend the dok-tidy target when building docs for the webserver.</p>
- </li>
- <li>
- <p>Add another plug for the privoxy-devel mailing list.</p>
- </li>
- <li>
- <p>Let the intro link the copyright section in the user manual instead of giving an incomplete summary of
- the license status.</p>
- </li>
- <li>
- <p>Clarify that the webserver target uploads to the SourceForge webserver.</p>
- </li>
- <li>
- <p>Mark the documentation for the Mac OS X installers as out of date and change the SCM name back to
- CVS.</p>
- </li>
- <li>
- <p>Fix the location of the installer modules for Mac OS X. They are not actually available through git
- (yet).</p>
- </li>
- <li>
- <p>Don't speak of Privoxy version 3 in the past tense.</p>
- </li>
- <li>
- <p>Update the list of programs required for the release process.</p>
- </li>
- <li>
- <p>Update description of the webserver target which uses ssh, not scp.</p>
- </li>
- <li>
- <p>Remove obsolete reference to config.new.</p>
+ <p>configure: Fix --with-msan option. Also (probably) reported by Andrew Savchenko.</p>
</li>
</ul>
</li>
<li>
- <p>Tests:</p>
+ <p>macOS build system:</p>
<ul>
<li>
- <p>Add another hide-referrer{conditional-block} test.</p>
- </li>
- <li>
- <p>Add another hide-referrer{conditional-forge} test.</p>
- </li>
- <li>
- <p>Fix a hide-referrer{conditional-forge} test that expected an acceptable header to be forged.</p>
- </li>
- <li>
- <p>Fix a hide-referrer{conditional-block} test that expected an acceptable Referer to be removed.</p>
- </li>
- <li>
- <p>Explain why the "Set Header = Host: whatever.example.org" test is expected to fail when using a CGI
- prefix that starts with "https://".</p>
- </li>
- <li>
- <p>Explain why a connection-sharing test is known to fail when using "https://p.p/" as CGI prefix.</p>
- </li>
- <li>
- <p>Add a link to Privoxy-Regression-Test to regression-tests.action in case it isn't packaged.</p>
- </li>
- <li>
- <p>Add regression tests for pcre host patterns.</p>
+ <p>Enable HTTPS inspection when building the macOS binary (using OpenSSL as TLS library).</p>
</li>
</ul>
</li>
<li>
- <p>Privoxy infrastructure:</p>
+ <p>Documentation:</p>
<ul>
<li>
- <p>Import a Privoxy logo for the website.</p>
+ <p>Add OpenSSL to the list of libraries that may be licensed under the Apache 2.0 license in which case the
+ linked Privoxy binary has to be distributed under the GPLv3 or later.</p>
</li>
<li>
- <p>Update Tor onion service to HiddenServiceVersion 3.</p>
+ <p>config: Fix the documented ca-directory default value. Reported by avoidr.</p>
</li>
<li>
- <p>Display the "model" photos in a single row and remove placeholder images.</p>
+ <p>Rebuild developer-manual and tidy with 'HTML Tidy for FreeBSD version 5.8.0'.</p>
</li>
<li>
- <p>Regenerate homepage with updated sponsor list.</p>
+ <p>Update developer manual with new macOS packaging instructions.</p>
</li>
<li>
- <p>Use the '/sponsor' redirect for the link to the sponsor page.</p>
+ <p>Note that the FreeBSD installation instructions work for ElectroBSD as well.</p>
</li>
<li>
- <p>Git commit messages are sent to the Privoxy-commits mailing list.</p>
+ <p>Note that FreeBSD/ElectroBSD users can try to install Privoxy as binary package using 'pkg'.</p>
</li>
</ul>
</li>
projects / privoxy.git / blobdiff