Check for valid values of: - [x] session.entropy_file - [ ] session.entropy_length - [ ] session.use_strict_mode - [x] session.use_only_cookies - [ ] session.cookie_lifetime - [x] session.use_trans_sid - [x] session.hash_function (set to 1) - [x] session.bug_compat_42 (set to 0) - [x] session.bug_compat_warn (set to 0) http://www.php.net/manual/en/session.configuration.php
Activity
enygma commentedon Nov 8, 2013
Should renaming the session cookie (PHPSESSID) be considered? I could see it being a "warning" item, but not a failure.
Merge pull request #37 from airbone42/master
xsist10 commentedon Jan 7, 2014
New merge pull #67 for:
session.hash_function (set to non-broken hashing mechanism)
session.bug_compat_42 (set to 0)
session.bug_compat_warn (set to 0)
sbusch commentedon Mar 17, 2014
See also here: https://stackoverflow.com/questions/5081025/php-session-fixation-hijacking