From git at git.privoxy.org Wed Jul 1 08:12:56 2026
From: git at git.privoxy.org (User Git)
Date: Wed, 01 Jul 2026 08:12:56 +0200
Subject: [Privoxy-commits] [privoxy] 03/03: faq.sgml: Fix a comment
In-Reply-To: <178288637358.81465.3726948675452765416@privoxy-git>
References: <178288637358.81465.3726948675452765416@privoxy-git>
Message-ID: <20260701061254.9B73EAF4F@git.privoxy.org>
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
commit 132ed56604dffa04dab904a3146d7dea56dc864c
Author: Fabian Keil
AuthorDate: Tue Jun 30 21:03:35 2026 +0200
faq.sgml: Fix a comment
---
doc/source/faq.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index b5f7004c..1f66548a 100644
--- a/doc/source/faq.sgml
+++ b/doc/source/faq.sgml
@@ -3176,7 +3176,7 @@ C:\Privoxy>
License
-
+
&license;
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
From git at git.privoxy.org Wed Jul 1 08:12:54 2026
From: git at git.privoxy.org (User Git)
Date: Wed, 01 Jul 2026 08:12:54 +0200
Subject: [Privoxy-commits] [privoxy] 01/03: faq.sgml: Fix markup
In-Reply-To: <178288637358.81465.3726948675452765416@privoxy-git>
References: <178288637358.81465.3726948675452765416@privoxy-git>
Message-ID: <20260701061254.36503AF83@git.privoxy.org>
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
commit df5d1d0f3eb6ab63917fba03f51a9e8a46c9df82
Author: Fabian Keil
AuthorDate: Tue Jun 30 20:56:31 2026 +0200
faq.sgml: Fix markup
---
doc/source/faq.sgml | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index b5ab5345..b5f7004c 100644
--- a/doc/source/faq.sgml
+++ b/doc/source/faq.sgml
@@ -612,13 +612,19 @@ warranty? Registration?
How can I confirm the Privoxy installer is genuine?
Each binary installation package is GPG signed by the relevant packager, using
- detached .asc signature files, as follows:
-
gpg --armor --output installer.sig --detach-sig installer
-
+ detached .asc signature files, as follows:
+
+
+ gpg --armor --output installer.sig --detach-sig installer
+
+
To verify that the installer file has not been modified since it was built,
- use GPG to check that it cryptographically matches the signature, as follows:
-
gpg --verify installer.sig installer
-
+ use GPG to check that it cryptographically matches the signature, as follows:
+
+
+ gpg --verify installer.sig installer
+
+
The output of this command will identify the email address of the packager,
alongside the fingerprint of their public GPG key. The current packagers are as
follows:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
From git at git.privoxy.org Wed Jul 1 08:12:53 2026
From: git at git.privoxy.org (User Git)
Date: Wed, 01 Jul 2026 08:12:53 +0200
Subject: [Privoxy-commits] [privoxy] branch master updated (f2c78701 ->
132ed566)
Message-ID: <178288637358.81465.3726948675452765416@privoxy-git>
This is an automated email from the git hooks/post-receive script.
git pushed a change to branch master
in repository privoxy.
from f2c78701 Update Windows supported versions and packageer GPG key info
new df5d1d0f faq.sgml: Fix markup
new 2f0043ec Regenerate FAQ
new 132ed566 faq.sgml: Fix a comment
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
doc/source/faq.sgml | 20 +++++++++++++-------
doc/webserver/faq/installation.html | 30 +++++++++++++++++++-----------
2 files changed, 32 insertions(+), 18 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
From git at git.privoxy.org Wed Jul 1 08:12:55 2026
From: git at git.privoxy.org (User Git)
Date: Wed, 01 Jul 2026 08:12:55 +0200
Subject: [Privoxy-commits] [privoxy] 02/03: Regenerate FAQ
In-Reply-To: <178288637358.81465.3726948675452765416@privoxy-git>
References: <178288637358.81465.3726948675452765416@privoxy-git>
Message-ID: <20260701061254.66815AF84@git.privoxy.org>
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
commit 2f0043ec8319790f378e6550b9209b27acc66dba
Author: Fabian Keil
AuthorDate: Tue Jun 30 20:57:28 2026 +0200
Regenerate FAQ
---
doc/webserver/faq/installation.html | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/doc/webserver/faq/installation.html b/doc/webserver/faq/installation.html
index 6467ba4c..67e2d932 100644
--- a/doc/webserver/faq/installation.html
+++ b/doc/webserver/faq/installation.html
@@ -30,13 +30,15 @@
Each binary installation package is GPG signed by the relevant packager, using detached .asc signature files,
- as follows: gpg --armor --output installer.sig --detach-sig installer To verify that the
- installer file has not been modified since it was built, use GPG to check that it cryptographically matches the
- signature, as follows: gpg --verify installer.sig installer The output of this command
- will identify the email address of the packager, alongside the fingerprint of their public GPG key. The current
- packagers are as follows:
+ as follows:
+ gpg --armor --output installer.sig --detach-sig installer
+ To verify that the installer file has not been modified since it was built, use GPG to check that it
+ cryptographically matches the signature, as follows:
+ gpg --verify installer.sig installer
+ The output of this command will identify the email address of the packager, alongside the fingerprint of their
+ public GPG key. The current packagers are as follows:
-
+
Table 1. Privoxy binary packagers
@@ -56,19 +58,25 @@
| FreeBSD |
Fabian Keil |
fk at fabiankeil.de |
- 4F36C17F3816913654A1E850691822918BA2371C |
+ 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C |
| Debian Linux |
Roland Rosenfeld |
roland at spinnaker.de |
- AC2FBDB104943D8A44A0211D02713BCFCA5410B2 |
+ AC2F BDB1 0494 3D8A 44A0 211D 0271 3BCF CA54 10B2 |
| macOS |
Ian Silvester |
iansilvester at fastmail.fm |
- 558FCF92D02E6325E6C89E8DD9A17F79A285F0C7 |
+ 558F CF92 D02E 6325 E6C8 9E8D D9A1 7F79 A285 F0C7 |
+
+
+ | Windows |
+ Lee Rian |
+ ler762 at gmail.com |
+ A64E FD41 6B94 82FD 3734 7AC9 F143 81F4 A112 856D |
@@ -94,7 +102,7 @@
issues.
It is preferable to build the latest code to target earlier OS
releases than use an earlier Privoxy release:
-
+
Table 2. Operating system support for binaries provided by Privoxy team members
@@ -114,7 +122,7 @@
| Windows |
- 3.0.33 |
+ 4.1.0 |
Windows 10 |
Windows Vista |
Intel 32 and 64 bit |
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
From git at git.privoxy.org Wed Jul 1 21:19:31 2026
From: git at git.privoxy.org (User Git)
Date: Wed, 01 Jul 2026 21:19:31 +0200
Subject: [Privoxy-commits] [privoxy] branch master updated: Correct filename
extensions for GPG signature files to match our standard
Message-ID: <178293357099.43882.4652110621980979668@privoxy-git>
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
The following commit(s) were added to refs/heads/master by this push:
new 54a9f89d Correct filename extensions for GPG signature files to match our standard
54a9f89d is described below
commit 54a9f89d6e154b583f69b5005e0cc44b2bafedd4
Author: Ian Silvester
AuthorDate: Wed Jul 1 15:18:45 2026 -0400
Correct filename extensions for GPG signature files to match our standard
---
doc/source/faq.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index 1f66548a..106af3dc 100644
--- a/doc/source/faq.sgml
+++ b/doc/source/faq.sgml
@@ -615,14 +615,14 @@ warranty? Registration?
detached .asc signature files, as follows:
- gpg --armor --output installer.sig --detach-sig installer
+ gpg --armor --output installer.asc --detach-sig installer
To verify that the installer file has not been modified since it was built,
use GPG to check that it cryptographically matches the signature, as follows:
- gpg --verify installer.sig installer
+ gpg --verify installer.asc installer
The output of this command will identify the email address of the packager,
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
From git at git.privoxy.org Thu Jul 2 14:48:43 2026
From: git at git.privoxy.org (User Git)
Date: Thu, 02 Jul 2026 14:48:43 +0200
Subject: [Privoxy-commits] [privoxy] branch master updated: Regenerate FAQ
Message-ID: <178299652341.37916.2844999894861838679@privoxy-git>
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
The following commit(s) were added to refs/heads/master by this push:
new 544adcf8 Regenerate FAQ
544adcf8 is described below
commit 544adcf84bd0af26a5835793d8c82bc9e4c4f599
Author: Fabian Keil
AuthorDate: Thu Jul 2 14:48:13 2026 +0200
Regenerate FAQ
---
doc/webserver/faq/installation.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/webserver/faq/installation.html b/doc/webserver/faq/installation.html
index 67e2d932..efcc9b26 100644
--- a/doc/webserver/faq/installation.html
+++ b/doc/webserver/faq/installation.html
@@ -31,10 +31,10 @@
genuine?
Each binary installation package is GPG signed by the relevant packager, using detached .asc signature files,
as follows:
- gpg --armor --output installer.sig --detach-sig installer
+ gpg --armor --output installer.asc --detach-sig installer
To verify that the installer file has not been modified since it was built, use GPG to check that it
cryptographically matches the signature, as follows:
- gpg --verify installer.sig installer
+ gpg --verify installer.asc installer
The output of this command will identify the email address of the packager, alongside the fingerprint of their
public GPG key. The current packagers are as follows:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.