75) Create a tool that creates Privoxy action (and filter?) files
out of adblock files. Could be implemented as option for
- url-pattern-translator.pl.
+ url-pattern-translator.pl. Before doing that, the already
+ existing solutions should probably be evaluated to see if
+ they do the job already or could be improved.
76) Cache DNS responses. Note that this has been requested
several times by users, but is not a developer priority.
86) Add a server-body-tagger action. This is trivial as as all the
functionality required to do it already exists.
-87) Add a client-body-tagger action. This, too, is trivial.
+87) Add a client-body-tagger action. Work in progress.
88) Investigate if there's a Perl module that Privoxy-Regression-Test
could optionally use to keep connections alive, preferably while
probably shouldn't be affected (such as actions like
forward-override). Investigate and fix or document.
-142) Remove or update the "internal" pcre version.
-
143) Add support for OpenBSD's pledge feature once it's stablelized.
This should be a lot less work then #124.
currently can result in client requests to config.privoxy.org on the
Internet which may not be desirable.
-150) Add blacklistd support.
+150) Add blocklistd support (https://man.netbsd.org/blocklistd.8).
151) Let the dok-tidy target work cross-platform without introducing
a ton of white-space changes that hide the content changes.
163) Use subdirectories in the certificate-directory to lower the number
of files per directory.
-164) Evaluate switching from pcreposix(3) to pcre's native api
- for URL matching which allows to compile the patterns once
- at load-time.
-
165) Add a max-connections-per-client directive.
-166) Figure out how to ship Windows binaries with external libraries
- like pcre and MbedTLS. Required for #142. Somewhat related:
- https://lists.privoxy.org/pipermail/privoxy-devel/2020-November/000400.html
-
167) Set up a public Privoxy-Filter-Test instance.
168) Add a privacy policy.
177) Support https-inspection for intercepted requests.
178) Warn on http://config.privoxy.org/client-tags if a Tag name
- has't at least one matching action section.
+ hasn't at least one matching action section.
179) Add a add-server-header{} action to add headers to the response
sent to the client (including responses generated by Privoxy itself).
when https inspecting while using a forwarding proxy.
184) Add support for wolfSSL. Work in progress, expected to be
- committed after the 3.0.32 release. Funded with donations
+ committed after the 3.0.34 release. Funded with donations
made to the Privoxy project.
185) The mbedTLS and OpenSSL versions of generate_host_certificate()
200) Add a config directive that causes Privoxy to remove all
host certificates before exiting.
+201) Add an action to change the trusted-cas-file for a section.
+ This should be useful in countries where a person-in-the-middle
+ attack is known to happen on some domains but should not be tolerated
+ on others. It would also allow to limit the accepted CA certificates
+ for given domains instead of accepting all that are specified with
+ the trusted-cas-file directive.
+
+202) Allow to use multiple log files with different debug settings.
+ Suggested by Jonathan Marten in FR#607.
+
+203) Add HTTP/2 support.
+
+204) Make the Privoxy website available over IPv6.
+
+205) Document how commit messages should look like.
+
##########################################################################
Hosting wish list (relevant for #53)