Does removing all filter files from the config file allow Privoxy to start with the policy enabled?
I suspect that the "'execmem' accesses" are the result of Privoxy requesting JIT-compilation (from pcre) if it's supported and the filter isn't dynamic.
JIT-support was introduced in Privoxy 3.0.29.
There currently is no convenient way to disable it dynamically but compiling with PCRE_STUDY_JIT_COMPILE undefined should disable it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does removing all filter files from the config file allow Privoxy to start with the policy enabled?
I suspect that the "'execmem' accesses" are the result of Privoxy requesting JIT-compilation (from pcre) if it's supported and the filter isn't dynamic.
JIT-support was introduced in Privoxy 3.0.29.
There currently is no convenient way to disable it dynamically but compiling with PCRE_STUDY_JIT_COMPILE undefined should disable it.
That seems to help. I'll ask if we can change the policy, if not, I'll rebuild with JIT disabled. Thanks!
You're welcome.
I've recently added a configure option to disable pcre JIT compilation:
https://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff;h=12f96cb705433afd5a14e6032adb5d12df8c23ca
Looks like the Fedora people adjusted the SELinux settings