#945 ca-directory keyword error

[Jim Dunn]

Hi, I had been using v3.x.x and upgraded to v4.0.0 last night. I noticed that I can no longer use the following keywords in the config.txt or I get an error on startup:

7.7.1. ca-directory
7.7.2. ca-cert-file
7.7.3. ca-key-file
7.7.4. ca-password
7.7.5. certificate-directory
7.7.6. cipher-list
7.7.7. trusted-cas-file

I used to use "ca-directory C:\Privoxy\certs" but no matter what I tried, it would always give me an error on startup. Has anyone else seen this??

[Fabian Keil]

What exactly is the error message you get?

Are you sure your Privoxy version has been compiled with FEATURE_HTTPS_INSPECTION? You can check at: http://config.privoxy.org/show-status

[Jim Dunn]

Oh no... YOU ARE RIGHT... I guess my v3.x.x was "compiled with FEATURE_HTTPS_INSPECTION"... but I didn't do it. Where can I find the v4.0.0 that HAS that FEATURE_HTTPS_INSPECTION based in ???

[Lee]

On Thu, Apr 3, 2025 at 7:55 AM Jim Dunn wrote:

Oh no... YOU ARE RIGHT... I guess my v3.x.x was "compiled with FEATURE_HTTPS_INSPECTION"... but I didn't do it. Where can I find the v4.0.0 that HAS that FEATURE_HTTPS_INSPECTION based in ???

I can put one up on sourceforge for you (and everyone else) or you can
follow the instructions at
https://www.privoxy.org/user-manual/installation.html#WINBUILD-CYGWIN
and build it yourself.

Fabian - I never figured out how to build wolfssl and openssl is still
a no-no for redistribution - correct?
So it's either somebody tells me how to build wolfssl or I put out a
privoxy release with mbed-tls

Lee

[Fabian Keil]

Building with MbedTLS for Windows sounds good to me.

Having said that, OpenSSL 3.x is licensed under the Apache License v2 so redistribution is no longer a no-no as the license is compatible with the GPLv3 and the Privoxy code is licensed GPLv2 or later which includes GPLv3.

The documentation could probable by more clear about this.

[Lee]

I just uploaded a Windows 4.0.0-1 release that supports https-inspection
That should resolve the problem

[Lee]

On Sat, Apr 5, 2025 at 2:34 PM Lee wrote:

I just uploaded a Windows 4.0.0-1 release that supports https-inspection
That should resolve the problem

I remember being able to close tickets on sourceforge. I seem to have
lost that ability :(

Lee

[Fabian Keil]

I remember being able to close tickets on sourceforge. I seem to have
lost that ability :(

Does it work now?

I checked the user permissions and you are part of the "Developer" group which has "update", "admin" and "create" permissions (all the permissions available) but "Developers" are also part of the "Member" group which had all the permissions removed. I changed the "Member" permissions to "update", "admin" and "create" .

[Lee]

yes! closed / fixed now