-
Notifications
You must be signed in to change notification settings - Fork 97
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
incorrect results / false positives #101
Comments
Hmm, interesting - I'll have to look into this one further to see what's happening here. There's "casting" functionality in the |
I encountered the same thing. +1 for fixing it. |
@enygma The cast is correct. It seems more an error with the "current value" column. Current value shows "0" but is definitly 1 ("On"). |
The bug is here: |
Hmm, trying to reproduce this one but it seems that things are reporting back correctly on a PHP 7.0 configuration file. I've tried:
Both seem to work as expected:
Is there something I'm missing to reproduce this issue? |
(discard warning about |
@tommy-muehle any update on how to reproduce this? |
@enygma I tried it also with my iniscan Docker container and this ini file. Here are the steps to reproduce:
Inside the container runs PHP 7.1 if this is necessary. |
For upload_max_filesize (16M -> 2M), post_max_size (24M -> 8M) and memory_limit (256M -> 128M) it returns me the default value and not the current value. For |
I guess there are some incorrect results. I use this php.ini and PHP 7.0 with iniscan version 3.6.4.
This is the output:
As you can read in the php docs the current session settings are secure.
allow_url_fopen
is also disabled. Or is the columnCurrent value
the recommended value?It seems the determination of default values is incorrect, because the value of
session.cookie_httponly
is""
. Same for other values.Do you check the values
1
,0
,Off
,On
,"1"
,"0"
or""
for specific settings?The text was updated successfully, but these errors were encountered: