Add #193: Use SHA256 instead of MD5 for the host hash

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 75951d3..a5ded2a 100644 (file)
--- a/TODO
+++ b/TODO
@@ -439,7 +439,7 @@ https://www.privoxy.org/donate
 169) Preserve all relevant copyright and license statements in binary
      packages we distribute.
 
 169) Preserve all relevant copyright and license statements in binary
      packages we distribute.
 

-170) Serve the ca-cert-file through the CGI interface so client's
+170) Serve the ca-cert-file through the CGI interface so clients

      can conveniently import it (insecurely).
 
 171) Create a "view page using Privoxy" website where users can input
      can conveniently import it (insecurely).
 
 171) Create a "view page using Privoxy" website where users can input


@@ -478,12 +478,42 @@ https://www.privoxy.org/donate
 183) Properly deal with proxy responses that arrive in multiple pieces
      when https inspecting while using a forwarding proxy.
 
 183) Properly deal with proxy responses that arrive in multiple pieces
      when https inspecting while using a forwarding proxy.
 

-184) Add support for wolfSSL. Work in progress.
+184) Add support for wolfSSL. Work in progress, expected to be
+     committed after the 3.0.30 release.

 
 

-185) The mbedTLS and OpenSSL version of generate_host_certificate()
+185) The mbedTLS and OpenSSL versions of generate_host_certificate()

      should only be called when necessary and the check should be
      done without holding the certificate mutex.
 
      should only be called when necessary and the check should be
      done without holding the certificate mutex.
 

+186) Privoxy should handle "OPTIONS *" requests properly.
+
+187) There should be a convenient way to see the versions of
+     the libraries Privoxy is using.
+
+188) In the windows config.txt file, add the line
+       user-manual ./doc/user-manual/
+     right after
+       # Copyright ...
+       #
+
+189) Bring back binary packages for macOS, preferably for both Intel and M1.
+     The first step would be getting at least one build system, either
+     donated or bought with donations earmarked for this.
+     Interested donors: 0.
+
+190) The socks5 authentication code should send user name an password
+     seperately or we should increase the cbuf size to allow longer
+     user names and passwords.
+
+191) The cipher-list directive should be split into cipher-list-server
+     and cipher-list-client.
+
+192) The client TLS contexts should probably be shared among threads
+     to spend less time and memory loading the root certificates.
+
+193) Use SHA256 instead of MD5 for the host hash used when generating file
+     names for host certificates and keys.
+

 ##########################################################################
 
 Hosting wish list (relevant for #53)
 ##########################################################################
 
 Hosting wish list (relevant for #53)