Hello all, I have looked into this and I'm inclined to go for a release note. Enabling MemoryDenyWriteExecute is a security enhancement, and while users can disable it as a workaround, I don't think the Ubuntu package should disable it by default - and diverge from Debian on that too.
d/apache2.NEWS, lines 45-50, say: MemoryDenyWriteExecute is set to yes by default. While this enhances security by preventing writable and executable memory regions, it may cause issues with modules that rely on JIT engines, such as mod_php with JIT-enabled PHP, mod_lua, or custom interpreters. In such cases, it is recommended to use PHP-FPM or FCGI modules instead. That is what we could hint in the release notes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2144455 Title: Apache's systemd option "MemoryDenyWriteExecute" breaks PHP JIT, under mod-php To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2144455/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
