- - Update example output.
- - Recommend the use of the https-inspection action in the documentation.
- - Upgrade a couple of URLs to https://.
- - Add ElectroBSD to the list of operating systems.
- - Bumped generated Firefox version to 78 (ESR).
- - Bumped version to 1.2.2.
-
- - User documentation:
- - Remove reference to 'How to Report Bugs Effectively'.
- It was only rendered as text without URL in the README anyway
- and there's no indication that users read it ...
- - Let the dok-readme target fix the location embedded into the
- README file. This used to be done by CVS but since the git migration
- it has to be done through other means.
- - Remove 'experimental' warning for client-specific-tag-related directives.
- They seem to work reliably and there is no obvious reason
- why we would change the syntax in the near future.
- - Describe how to check if Privoxy has been built with
- FEATURE_HTTPS_INSPECTION.
- - Add a link to the trusted-cas-file documentation
- that explains how the user can create the file herself.
- - Don't explicitly mention the license for the code coming from
- 'Anonymous Coders' and Junkbusters. It's obviously licensed under
- the GNU GPL like the rest of Privoxy or we wouldn't be allowed to
- distribute it.
- - Update the +hide-user-agent example with uagen output.
- - Slightly improve the wording of the ca-key-file documentation.
- - Explicitly mention Windows 10 as supported so search engines and
- users looking for it can find it.
- - Import a bunch of contributors from the ChangeLog.
- - Remove obsolete doc/gpl.html.
- - Upgrade a couple of links to https://.
- - Don't prefer the SourceForge patch tracker over the
- privoxy-devel mailing list. While at it, link to the
- SourceForge patch tracker.
- - Mention http-inspection in the 'my browser warns me about
- unauthenticated content' FAQ entry.
- - Simplify the 'Is there is a license or fee?' FAQ entry.
- - Add another +redirect{} example.
- - Explicitly mention that interested sponsors should include
- the link target in their first mail.
- - Clarify that only Privoxy team members can object to new sponsors
- and link to the list of current team members.
- - Note that sponsor URLs may not contain keyword spam.
- - Garbage collect doc/webserver/images which isn't referenced anymore.
- - Update the method to reach the proxy settings in Firefox.
- - Update proxy_setup.jpg description to refer to Firefox.
- - Regenerate proxy_setup.jpg with a more recent Firefox (78.0).
- - Regenerate files-in-use.jpg without obsolete standard.action
- with modern colors and a slightly better quality.
- - Update URL to the actionsfile tracker.
- - Update a support request URL.
- - Rephrase the 'Can Privoxy run as service' FAQ entry and
- remove an obsolete paragraph.
- - Let the 'Where can I get updated Actions Files?' entry link to
- the gitweb version of default.action.master.
- - Update a link to the default.action file.
- - Update URLs for trackers and mailing lists.
- - Replace CVS reference with git.
- - Mention regression-tests.action in the config file.
- - Explicitly mention in the config file that access to the
- CA key should be limited to Privoxy.
- - List more client-specific-tag examples for inspiration.
- - Add additional headers to the client-header-order example.
- - Note that actions aren't updated after rewrites.
- - Explicitly mention that upgrading from http to https with
- a client-header filter is not supported
- - Note that protocol and host have to be added when rewriting
- the destination host for https-inspected requests.
- - Explicitly mention that the CA key is used to sign certificates.
- - Put openssl command in 'command' tags.
- - The man page has been moved from section 1 to man section 8.
-
-- Developer manual:
- - Flesh out the build instructions for Debian.
- - Remove the packaging instructions for RPM-based systems.
- They don't work and we don't release RPM packages anymore anyway.
- - Remove the packaging instructions for Solaris.
- They don't work and we don't release Solaris packages anymore anyway.
- - Update the suggested subject for the announce mails.
- - Update upload instructions.
- ftp://upload.sourceforge.net is no longer functional.
- - Remove a couple of package-dependent upload instructions
- that don't actually work.
- - Remove 'cd current' that no longer works.
- - Add regression-tests.action to the list of files that should be installed.
- - Stop claiming that there are text versions of the manuals.
- We stopped building them in 2008 (9ed36a3c5e6f12).
- - Note that the 'webserver' target creates the link needed for the user-manual.
- - Suggest to use the master branch as reference when creating
- the ChangeLog so the steps work when the current branch differs
- from master which is likely as the developer manual
- suggests to use a local branch for development.
- - Add the -s flag to the suggested 'git tag' command. We prefer signed tags.
- - Mention that merges into 'master' should be avoided.
- - Add git commands that should result in a merge-free history.
- - Mention Privoxy-Regression-Test.
- - Add a section id to reduce link churn.
- - Recommend the dok-tidy target when building docs for the webserver.
- - Add another plug for the privoxy-devel mailing list.
- - Let the intro link the copyright section in the user manual instead
- of giving an incomplete summary of the license status.
- - Clarify that the webserver target uploads to the SourceForge webserver.
- - Mark the documentation for the Mac OS X installers as out of date and
- change the SCM name back to CVS.
- - Fix the location of the installer modules for Mac OS X.
- They are not actually available through git (yet).
- - Don't speak of Privoxy version 3 in the past tense.
- - Update the list of programs required for the release process.
- - Update description of the webserver target which uses ssh, not scp.
- - Remove obsolete reference to config.new.
-
-- Tests:
- - Add another hide-referrer{conditional-block} test.
- - Add another hide-referrer{conditional-forge} test.
- - Fix a hide-referrer{conditional-forge} test
- that expected an acceptable header to be forged.
- - Fix a hide-referrer{conditional-block} test
- that expected an acceptable Referer to be removed.
- - Explain why the "Set Header = Host: whatever.example.org" test is
- expected to fail when using a CGI prefix that starts with "https://".
- - Explain why a connection-sharing test is known to fail
- when using "https://p.p/" as CGI prefix.
- - Add a link to Privoxy-Regression-Test to regression-tests.action
- in case it isn't packaged.
- - Add regression tests for pcre host patterns.
-
-- Privoxy infrastructure:
- - Import a Privoxy logo for the website.
- - Update Tor onion service to HiddenServiceVersion 3.
- - Display the "model" photos in a single row and remove placeholder images.
- - Regenerate homepage with updated sponsor list.
- - Use the '/sponsor' redirect for the link to the sponsor page.
- - Git commit messages are sent to the Privoxy-commits mailing list.
+ - Bump version to 1.2.4.
+ - Update BROWSER_VERSION and BROWSER_REVISION to 102.0
+ to match the User-Agent of the current Firefox ESR.
+ - Explicitly document that changing the 'Gecko token' is suspicious.
+ - Consistently use a lower-case 'c' as copyright symbol.
+ - Bump copyright.
+ - Add 'aarch64' as Linux architecture.
+ - Add OpenBSD architecture 'arm64'.
+ - Stop using sparc64 as FreeBSD architecture.
+ It hasn't been supported for a while now.
+
+- Build system:
+ - 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.
+ - configure: Fix --with-msan option.
+ Also (probably) reported by Andrew Savchenko.
+
+- macOS build system:
+ - Enable HTTPS inspection when building the macOS binary
+ (using OpenSSL as TLS library).
+
+- Documentation:
+ - 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.
+ - config: Fix the documented ca-directory default value.
+ Reported by avoidr.
+ - Rebuild developer-manual and tidy with 'HTML Tidy for FreeBSD version 5.8.0'.
+ - Update developer manual with new macOS packaging instructions.
+ - Note that the FreeBSD installation instructions work for
+ ElectroBSD as well.
+ - Note that FreeBSD/ElectroBSD users can try to install Privoxy
+ as binary package using 'pkg'.