[Privoxy-commits] [privoxy] 01/02: user-manual: Sync paragraph explaining the license of Privoxy binaries

[User Git]

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch master
in repository privoxy.

commit 18e26f4ccf0abcfe6de37d165c9234d8a4d8e9f9
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Tue Jan 6 07:54:56 2026 +0100

    user-manual: Sync paragraph explaining the license of Privoxy binaries
    
    ... when linked to a recent TLS library with license.sgml
    which currently isn't properly included but should be.
---
 doc/source/user-manual.sgml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index 4a6d5003..ddafcd96 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -8520,8 +8520,11 @@ Requests</title>
 <para>
  The same is true for <application>Privoxy</application> binaries
  unless they are linked with a
- <ulink url="https://www.trustedfirmware.org/projects/mbed-tls/">mbed TLS</ulink> version
- that is licensed under the Apache 2.0 license in which
+ <ulink url="https://www.trustedfirmware.org/projects/mbed-tls/">mbed TLS</ulink> or
+ <ulink url="https://www.openssl.org/">OpenSSL</ulink> version
+ that is licensed under the Apache 2.0 license or against a
+ <ulink url="https://github.com/wolfSSL/wolfssl/">wolfSSL</ulink> version
+ that is licensed under the GPL 3 in which
  case you can redistribute and/or modify the <application>Privoxy</application>
  binaries under the terms of the <citetitle>GNU General Public License</citetitle>
  as published by the Free Software Foundation, either version 3

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.