diff --git a/docs/config_file_description/README.md b/docs/config_file_description/README.md index 430beea2..d192d4cd 100644 --- a/docs/config_file_description/README.md +++ b/docs/config_file_description/README.md @@ -267,7 +267,11 @@ to request Anti-bot Challenge again mode: LOG # available modes: php_immunity: False -# enable (True) or disable (False (default)) PHP Immunity (allows to automatically detect & patch vulnerabilities in software at the Proactive Defense level preventing re-infections through the same vulnerability). By enabling this feature, Blamer will be enabled as well and Proactive Defence switched into the KILL mode. +# enable (True) or disable (False (default)) PHP Immunity (allows to automatically detect & patch vulnerabilities in software at the Proactive Defense level preventing re-infections through the same vulnerability). By enabling this feature, Blamer will be enabled as well and Proactive Defence switched into the KILL mode. +jit_compatible_mode: True +# For PHP 8.0+, if the key is omitted or null in the merged config, the extension enables JIT-compatible mode by default. Set to False to disable it explicitly. When enabled, Proactive Defense uses a hooking path compatible with PHP OPcache JIT. +log_whitelisted: False +# enable (True) or disable (False (default)) logging of whitelisted events. When enabled, Proactive Defense will log events even for whitelisted scripts, which can be useful for auditing purposes. MALWARE_SCAN_INTENSITY: diff --git a/docs/dashboard/README.md b/docs/dashboard/README.md index 0042c6db..fe206769 100644 --- a/docs/dashboard/README.md +++ b/docs/dashboard/README.md @@ -973,13 +973,18 @@ Starting from PHP 8, the interpreter supports `opcache.jit` option to enable jus When the Proactive Defense extension (or any other PHP extensions that use the hooks to intercept function calls) is enabled, opcache engine disables `opcache.jit` automatically and reports it into the error log. It does not affect the stability and performance of websites running PHP 8 when both `opcache.jit` and the Proactive Defense module are enabled, but the JIT will be off. -To keep `opcache.jit` forcibly enabled and keep the Proactive Defense module enabled, one needs to add the following config option: +To keep `opcache.jit` forcibly enabled and keep the Proactive Defense module enabled, set jit_compatible_mode to True under the PROACTIVE_DEFENCE section in the Imunify360 configuration file (merged config), for example: +```yaml +PROACTIVE_DEFENCE: + jit_compatible_mode: True ``` -jit_compatible_mode=on -``` -in the `/usr/share/i360-php-opts/module.ini` file. +The merged config is typically at /etc/sysconfig/imunify360/imunify360-merged.config (or the non-privileged variant when used). See also [Config file description](/config_file_description/) for the full list of PROACTIVE_DEFENCE options. + +::: tip Note +The PHP extension applies jit_compatible_mode from the merged Imunify360 YAML configuration (not from module.ini). Older documentation referred to module.ini; use PROACTIVE_DEFENCE.jit_compatible_mode in the merged config as shown above. +::: ## Reputation Management