- Announcing Privoxy 3.0.27 stable
+ Announcing Privoxy 3.0.31 stable
--------------------------------------------------------------------
-Privoxy 3.0.27 stable scales better in multi-user environments
-and brings a couple of tuning directives.
+Privoxy 3.0.31 fixes two security issues that were discovered while
+preparing the 3.0.30 release. The issues also affect earlier Privoxy
+releases.
+
--------------------------------------------------------------------
-ChangeLog for Privoxy
+ChangeLog for Privoxy 3.0.31
+--------------------------------------------------------------------
+- Security/Reliability:
+ - Prevent an assertion from getting triggered by a crafted CGI request.
+ Commit 5bba5b89193fa. OVE-20210130-0001.
+ Reported by: Joshua Rogers (Opera)
+ - Fixed a memory leak when decompression fails "unexpectedly".
+ Commit f431d61740cc0. OVE-20210128-0001.
+
+- Bug fixes:
+ - Fixed detection of insufficient data for decompression.
+ Previously Privoxy could try to decompress a partly
+ uninitialized buffer.
+
+--------------------------------------------------------------------
+ChangeLog for Privoxy 3.0.30
--------------------------------------------------------------------
-- General improvements:
- - Add a receive-buffer-size directive which can be used to
- set the size of the previously statically allocated buffer
- in handle_established_connection().
- Increasing the buffer size increases Privoxy's memory usage but
- can lower the number of context switches and thereby reduce the
- CPU usage and potentially increase the throughput.
- This is mostly relevant for fast network connections and
- large downloads that don't require filtering.
- Sponsored by: Robert Klemme
- - Add a listen-backlog directive which specifies the backlog
- value passed to listen().
- Sponsored by: Robert Klemme
- - Add an enable-accept-filter directive which allows to
- toggle accept filter support at run time when compiled
- with FEATURE_ACCEPT_FILTER support.
- It makes testing more convenient and now that it's
- optional we can emit an error message if enabling
- the accept filter fails.
- Sponsored by: Robert Klemme
- - Add a delay-response{} action.
- This is useful to tar pit JavaScript requests that
- are endlessly retried in case of blocks. It can also
- be used to simulate a slow Internet connection.
- Sponsored by: Robert Klemme
- - Add a 'trusted-cgi-referrer' directive.
- It allows to configure another page or site that can be used
- to reach sensitive CGI resources.
- Sponsored by: Robert Klemme
- - Add a --fuzz mode which exposes Privoxy internals to input
- from files or stdout.
- Mainly tested with American Fuzzy Lop. For details see:
- https://www.fabiankeil.de/talks/fuzzing-on-freebsd/
- This work was partially funded with donations and done
- as part of the Privoxy month in 2015.
- - Consistently use the U(ngreedy) flag in the 'img-reorder' filter.
- - listen_loop(): Reuse a single thread attribute object
- The object doesn't change and creating a new one for
- every thread is a waste of (CPU) time.
- Sponsored by: Robert Klemme
- - Free csp resources in the thread that belongs to the csp instead
- of the main thread which has enough on its plate already.
- Sponsored by: Robert Klemme
- - Improve 'socket timeout reached' message.
- Log the timeout that was triggered and downgrade the
- log level to LOG_LEVEL_CONNECT to reduce the log noise
- with common debug settings.
- The timeout isn't necessary the result of an error and
- usually merely indicates that Privoxy's socket timeout
- is lower than the relevant timeouts used by client and
- server.
- Sponsored by: Robert Klemme
- - Explicitly taint the server socket in case of CONNECT requests.
- This doesn't fix any known problems, but makes
- some log messages less confusing.
- - Let write_pid_file() terminate if the pid file can't be opened.
- Logging the issue at info level is unlikely to help.
- - log_error(): Reduce the mutex-protected area by not using a
- heap-allocated buffer that is shared between all threads.
- This increases performance and reduces the latency with
- verbose debug settings and multiple concurrent connections.
- Sponsored by: Robert Klemme
- - Let zalloc() use calloc() if it's available.
- In some situations using calloc() can be faster than
- malloc() + memset() and it should never be slower.
- In the real world the impact of this change is not
- expected to be noticeable.
- Sponsored by: Robert Klemme
- - Never use select() when poll() is available.
- On most platforms select() is limited by FD_SETSIZE while
- poll() is not. This was a scaling issue for multi-user setups.
- Using poll() has no downside other than the usual risk
- that code modifications may introduce new bugs that have
- yet to be found and fixed.
- At least in theory this commit could also reduce the latency
- when there are lots of connections and select() would use
- "bit fields in arrays of integers" to store file descriptors.
- Another side effect is that Privoxy no longer has to stop
- monitoring the client sockets when pipelined requests are
- waiting but can't be read yet.
- This code keeps the select()-based code behind ifdefs for
- now but hopefully it can be removed soonish to make the
- code more readable.
- Sponsored by: Robert Klemme
- - Add a 'reproducible-tarball-dist' target.
- It's currently separate from the "tarball-dist" target
- because it requires a tar implementation with mtree spec
- support.
- It's far from being perfect and does not enforce a
- reproducible mode, but it's better than nothing.
- - Use arc4random() if it's available.
- While Privoxy doesn't need high quality pseudo-random numbers
- there's no reason not to use them when we can and this silences
- a warning emitted by code checkers that can't tell whether or not
- the quality matters.
- - Show the FEATURE_EXTERNAL_FILTERS status on the status page.
- Better late than never. Previously a couple of tests weren't
- executed as Privoxy-Regression-Test couldn't detect that the
- FEATURE_EXTERNAL_FILTERS dependency was satisfied.
- - Ditch FEATURE_IMAGE_DETECT_MSIE.
- It's an obsolete workaround we inherited from Junkbuster
- and was already disabled by default.
- Users that feel the urge to work around issues with
- image requests coming from an Internet Explorer version
- from more than 15 years ago can still do this using tags.
- - Consistently use strdup_or_die() instead of strdup() in
- cases where allocation failures aren't expected.
- Using strdup_or_die() allows to remove a couple of explicit
- error checks which slightly reduces the size of the binary.
- - Insert a refresh tag into the /client-tags CGI page when
- serving it while a client-specific tag is temporarily enabled.
- This makes it less likely that the user ends up
- looking at tag state that is out of date.
- - Use absolute URLs in the client-tag forms.
- It's more consistent with the rest of the CGI page
- URLs and makes it more convenient to copy the forms
- to external pages.
- - cgi_error_disabled(): Use status code 403 and an appropriate response line
- - Use a dedicated CGI handler to deal with tag-toggle requests
- As a result the /client-tags page is now safe to reach without
- trusted Referer header which makes bookmarking or linking to
- it more convenient.
- Finally, refreshing the /client-tags page to show the
- current state can no longer unintentionally repeat the
- previous toggle request.
- - Don't add a "Connection" header for CONNECT requests.
- Explicitly sending "Connection: close" is not necessary and
- apparently it causes problems with some forwarding proxies
- that will close the connection prematurely.
- Reported by Marc Thomas.
- - Fix compiler warnings.
- Bug fixes:
- - rfc2553_connect_to(): Properly detect and log when poll()
- reached the time out. Previously this was logged as:
- Could not connect to [...]: No error: 0.
- which isn't very helpful.
+ - 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.
+ - Let the hide-referrer code tolerate Referer headers with https:// URLs.
+ Previously they would always be treated like a changed host.
+ - 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.
+ - 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.
+ - Support using https-inspection and client-header-order at the same time.
+ Previously Privoxy would crash.
+ Reported by: Kai Raven
+ - 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.
+ - 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.
+ - Let the uninstall target remove the config file even if DESTDIR
+ is set and properly announce the deletion of the configuration files.
+
+- General improvements:
+ - 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.
+ - 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
+ - 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
- - add_tag_for_client(): Set time_to_live properly.
- Previously the time_to_live was always set for the first tag.
- Attempts to temporarily enable a tag would result in enabling
- it permanently unless no tag was enabled already.
- - Revert r1.165 which didn't perform as advertised.
- While the idea was to use "https:// when creating links
- for the user manual on the website", the actual effect
- was to use "https://" when Privoxy was supposed to serve
- the user manual itself.
- Reported by Yossi Zahn on Privoxy-devel@.
- - socks5_connect(): Fail in case of unsupported address types.
- Previously they would not be detected right away and
- Privoxy would fail later on with an error message that
- didn't make it obvious that the problem was socks-related.
- So far, no such problems have actually been reported.
- - socks5_connect(): Properly deal with socks replies that
- contain IPv6 addresses.
- Previously parts of the reply were left unread and
- later on treated as invalid HTTP response data.
- Fixes #904 reported by Danny Goossen who also provided
- the initial version of this patch.
+ - 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.
+ - Recycle debug bit 4 for Tagging-related messages.
+ - Improve the message shown when the client-tags CGI page
+ is requested with no tags configured.
+ - 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.
+ - 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.
+ - The code compiles with older C compilers again.
+ - The chdir() return code is checked to fix a compiler warning.
+ - 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.
+ - Fixed harmless compiler warnings from GCC9 with -D_FORTIFY_SOURCE=2.
+ - windows: Remove obsolete '$(DEST)/doc/images' target.
+ - windows: Install the images referenced in the user manual.
+ - Remove obsolete 'gnu_regex.@OBJEXT@' target.
+ - 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.
+ - Add new FEATURES to the show-status page and resort list.
+ - Remove unused variable in the OpenSSL-specific code.
+ - Update bug tracker URL in cgi_error_unknown().
+ - Saved a couple of memory allocations when sorting client headers.
+ - Improved a couple of error messages.
+ - Saved memory allocations when using OpenSSL and checking if a
+ key already exists.
+ - The configure script will bail out if OpenSSL and mbedTLS are
+ enabled at the same time.
+ - Log a message right before exiting gracefully.
+ - A couple of structures have been rearranged to require slightly
+ less memory.
+ - When https inspection is enabled and the certificate is invalid
+ the error message is now sent with status code 403 instead of 200.
+ - The Slackware rc script template has been renamed to
+ slackware/rc.privoxy.in to silence complaints when building
+ Debian packages.
+ - 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.
- Action file improvements:
- - Unblock 'msdn.microsoft.com/'.
- It (presumably) isn't used to serve the kind of ads Privoxy should
- block by default but happens to serve lots of pages with URLs that
- are likely to result in false positives.
- Reported by bugreporter1694 in AF#939.
- - Disable gif deanimation for requests tagged with CSS-REQUEST.
- The action will ignore content that isn't considered text
- anyway and explicitly disabling it makes this more obvious
- if "action" debugging (debug 65536) is enabled while
- "gif deanimation" debugging (debug 256) isn't.
- - Explicitly disable HTML filters for requests with CSS-REQUEST tag.
- The filters are unlikely to break CSS files but executing
- them without (intentionally) getting any hits is a waste of
- cpu time and makes the log more noisy when running with
- "debug 64".
- - Unblock 'adventofcode.com/'.
- Reported by Clint Adams in Debian bug #848211.
- Fixes Roland's AF#937.
- - Unblock 'adlibris.com'.
- Reported by Wyrex in #935
- - Unblock .golang.org/
- - Add fast-redirects exception for '.youtube.com/.*origin=http'
+ - Block requests to eu-tlp03.kameleoon.com/.
+ - Unblock metrics.sr.ht/.
+ - Disable fast-redirects for .fsf.org/.
+ - Disable fast-redirects for .gravater.com/.
+ - Disable fast-redirects for .ksta.de/.
+ - Block requests to tag.crsspxl.com/.
+ - Block requests to analytics.slashdotmedia.com/.
+ - Block requests to ml314.com/.
+ - Block requests to .adroll.com/.
+ - Block requests to fastlane.rubiconproject.com/.
+ - Block requests to api.theadex.com/.
+ - Block requests to ih.adscale.de/.
+ - Block requests to .s400.meetrics.net/.
+ - Block requests for pp.lp4.io/.
+ - Block requests for trc-events.taboola.com/.
+
+- Filter file improvements:
+ - 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.
+ - Added an imdb filter.
+ - Added a sourceforge filter that reduces the amount of ads
+ for proprietary software.
+ - Added a github filter that removes the annoying "Sign-Up"
+ banner and the Cookie disclaimer.
+ - Removed a duplicated pcrs command from the js-annoyances filter.
+ - 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.
- Privoxy-Log-Parser:
- - Don't gather host and resource statistics if they aren't requested.
- While the performance impact seems negligible this significantly
- reduces the memory usage if there are lots of requests.
- - Bump version as the behaviour (slightly) changed.
- - Count connection failures as well in statistics mode.
- Sponsored by: Robert Klemme
- - Count connection timeouts as well in statistics mode.
- Sponsored by: Robert Klemme
- - Fix an 'uninitialized value' warning when generating
- statistics for a log file without response headers.
- While privoxy-log-parser was supposed to detect this already,
- the check was flawed and the message the user didn't see was
- somewhat confusing anyway.
- Now the message is less confusing, more helpful and actually printed.
- Reported by: Robert Klemme
-
-- Documentation improvements:
- - Refer to the git sources instead of CVS.
- - Use GNU/Linux when referring to the OS instead of the kernel.
- - Add FAQ entry for what to do if editing the config file is access denied.
- - Add brief HTTP/2 FAQ.
- - Add a small fuzzing section to the developer documentation.
- - Add a client-header-tagger{client-ip-address} example.
- - Stop suggesting that Privoxy is an anonymizing proxy.
- The term could lead to Privoxy users overestimating
- what it can do on its own (without Tor).
- - Make it more obvious that SPI accepts Paypal, too.
- Currently most donations are made through the Paypal account
- managed by Zwiebelfreunde e.V. and a more even distribution
- would be useful.
- - Suggest to log applying actions as well when reproducing problems.
- - Explicitly mention that Privoxy binaries are built by individuals
- on their own systems. Buyer beware!
- - Mention the release feed on the homepage.
- - Remove a mysterious comment with a GNU FDL link as it isn't
- useful and could confuse license scanners.
- In May 2002 it was briefly claimed that "this document" was covered
- by the GNU FDL. The commit message (r1.5) doesn't explain the motivation
- or whether all copyright holders were actually asked and agreed to the
- declared license change.
- It's thus hard to tell whether or not the license change was legit,
- but luckily two days later the "doc license" was "put" "back to GPL"
- anyway (r1.6).
- At the same time the offending comment with a link to the FDL
- (not the GPL) was added for no obvious reason.
- Now it's gone again.
-
-- Regression tests:
- - Bump for-privoxy-version to 3.0.27 as we now rely on untrusted
- CGI request being rejected with status code 403 (instead of 200).
- - Update test for /send-stylesheet and add another one
-
-- Templates:
- - Consistently use https:// when linking to the Privoxy website.
- - Remove SourceForge references in Copyright header.
- - Remove a couple of SourceForge references in a comment.
- While at it, fix the grammar.
- - Move the site-specific documentation block before the generic one.
- While most Privoxy installations don't have a site-specific
- documentation block, in cases were it exists it's likely to
- be more relevant than the generic one.
- Showing it first makes it less likely that users stop reading
- before they reach it, especially on pages that don't fit on
- the screen.
-
-- Build system improvements:
- - Prefer openjade to jade. On some systems Jade produces
- HTML with unescaped ampersands in URLs.
- - Prefer OpenSP to SP to be consistent.
- - Have Docbook generated HTML files be straight ASCII.
- Dealing with a mixture of ISO-8859 and UTF-8 files is problematic.
- - Echo the filename to stderr for 'make dok-tidy'.
- Make it a bit easier to find errors in docbook generated HTML.
- - Warn when still using select().
- - Warn when compiling without calloc().
- - Make it more obvious that the --with-fdsetsize configure switch
- is pointless if poll() is available.
- - Remove support for AmigaOS.
- - Update windows build system to use supported software.
- The cygwin gcc -mno-cygwin option is no longer supported, so
- convert the windows build system to use the cygwin cross-compiler
- to build "native" code.
- - Add --enable-static-linking option for configure
- does the same thing as LDFLAGS=-static; ./configure
- but nicer than mixing evars and configure options.
+ - Highlight a few more messages.
+ - Add a handler for tagging messages.
+ - Properly deal with 'Certificate error' crunches
+ Previously the error description was highlighted as 'host'.
+ - Log truncated LOG_LEVEL_CLF messages more gracefully
+ and note that the statistics will be imprecise.
+ - Fixed perldoc typo.
+ - Bump version to 0.9.2.
+
+- Privoxy-Regression-Test:
+ - Use http://127.0.0.1:8118/ as default Privoxy address
+ unless http_proxy is set through the environment.
+ - 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.
+ - 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.
+ - Use --proxy-header when using a CGI prefix with https://
+ and a "Host:" header.
+ - Allow '|' in tokens and values to allow tag patterns like
+ "TAG:^(application|text)/(x-)?javascript$".
+ - When get_cgi_page_or_else() fails, include the URL of the
+ requested page in the log message.
+ - 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.
+ - Bumped version to 0.7.2
+
+- uagen:
+ - 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.
+ - Fixed a regression test that is executed when
+ FEATURE_GRACEFUL_TERMINATION is enabled.
+
+- 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.
-----------------------------------------------------------------
About Privoxy:
Our TODO list is rather long. Helping hands and donations are welcome:
- * https://www.privoxy.org/faq/general.html#PARTICIPATE
+ * https://www.privoxy.org/participate
- * https://www.privoxy.org/faq/general.html#DONATE
+ * https://www.privoxy.org/donate
At present, Privoxy is known to run on Windows 95 and later versions
-(98, ME, 2000, XP, Vista, Windows 7 etc.), GNU/Linux (RedHat, SuSE,
-Debian, Fedora, Gentoo, Slackware and others), Mac OS X (10.4 and
-upwards on PPC and Intel processors), OS/2, Haiku, DragonFly, ElectroBSD,
-FreeBSD, NetBSD, OpenBSD, Solaris, and various other flavors of Unix.
+(98, ME, 2000, XP, Vista, Windows 7, Windows 10 etc.), GNU/Linux
+(RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and others),
+Mac OS X (10.4 and upwards on PPC and Intel processors), Haiku,
+DragonFly, ElectroBSD, FreeBSD, NetBSD, OpenBSD, Solaris,
+and various other flavors of Unix.
In addition to the core features of ad blocking and cookie management,
Privoxy provides many supplemental features, that give the end-user
* Supports tagging which allows to change the behaviour based on client
and server headers.
+ * Supports https inspection which allows to filter https requests.
+
* Can be run as an "intercepting" proxy, which obviates the need to
configure browsers individually.
projects / privoxy.git / blobdiff