-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lynis 2.0 expose_php false detection ? #27
Comments
also my additional .ini files registered by PHP configscandir compile option
you could add that to array of .ini files you check for php.ini which you grep for any checked php variables like expose_php and make sure those get higher priority over php.ini as they would potentially override php.ini values ? although simple
would be easier |
how to set "expose_php = Off" in Debian server ? |
Correction to initial bug report, What's going on here is similar to psecio/iniscan#82 where PHP settings can be defined in additional php -i | grep expose Will work for the |
This item is "on hold", as it is hard to parse them properly. We will do more research later, to see if we can create a reliable way to parse different PHP configurations and keep the versions in mind as well. |
Closing this issue, to clean up a little bit. Right now, no changes are made to the PHP scanning logic, as it needs a rewrite. |
I ran lynis 2.0 on a CentOS 7 server installed with my custom CentminMod.com LEMP stack where Nginx and PHP-FPM are source compiled.
Lynis detects and reports expose_php is ON while in fact it is OFF
check PHPINFO
PHP-FPM install has custom settings set in configscandir defined at PHP compile time
this overrides the default php.ini set expose_php value
so maybe extend the check to grep php -i output ?
The text was updated successfully, but these errors were encountered: