SMF 2.0.16+ cookie changes
Hello all!
With SMF 2.0.16 we have introduced an important security change for our cookies. This change will also be in the next release of SMF 2.1.
We now generate an HMAC for parts of the cookie using an authentication sercet only known by the server. This prevents forgeries of the cookie by any would-be attacker.
This change breaks backwards compatibility with cookies for 2.0.15 and below. Therefore, integrations and modifications that need to tap into SMF's cookie will need to be updated.
To support both the new and the old cookie hashes, you may use this code:
require_once($sourcedir . '/Load.php');
// Use strong cookie
if (function_exists('get_auth_secret'))
// Fallback for older versions
else
The get_auth_secret() function, which is part of Load.php, was introduced in 2.0.16 to ease the generation and retrieval of the authentication secret. If that function exists, your code will know that it should use the new password hash in the cookie. If it does not, your code should use the old hash.
Because we know that not all mods can be updated immediately, we've included a setting in the 2.0.16 admin control panel to allow the admin to disable the new cookie security for the sake of backwards compatibility with outdated mods. This setting is only available when a mod that uses the 'integrate_verify_user' hook is installed. This setting will be removed in future versions of SMF; it is only intended as a stop-gap measure until mod authors have time to update their code.
Thanks for reading!
With SMF 2.0.16 we have introduced an important security change for our cookies. This change will also be in the next release of SMF 2.1.
We now generate an HMAC for parts of the cookie using an authentication sercet only known by the server. This prevents forgeries of the cookie by any would-be attacker.
This change breaks backwards compatibility with cookies for 2.0.15 and below. Therefore, integrations and modifications that need to tap into SMF's cookie will need to be updated.
To support both the new and the old cookie hashes, you may use this code:
require_once($sourcedir . '/Load.php');
// Use strong cookie
if (function_exists('get_auth_secret'))
$hashed_password = hash_hmac('sha1', sha1($user_info['passwd'] . $user_info['password_salt']), get_auth_secret());
// Fallback for older versions
else
$hashed_password = sha1($user_info['passwd'] . $user_info['password_salt']);
The get_auth_secret() function, which is part of Load.php, was introduced in 2.0.16 to ease the generation and retrieval of the authentication secret. If that function exists, your code will know that it should use the new password hash in the cookie. If it does not, your code should use the old hash.
Because we know that not all mods can be updated immediately, we've included a setting in the 2.0.16 admin control panel to allow the admin to disable the new cookie security for the sake of backwards compatibility with outdated mods. This setting is only available when a mod that uses the 'integrate_verify_user' hook is installed. This setting will be removed in future versions of SMF; it is only intended as a stop-gap measure until mod authors have time to update their code.
Thanks for reading!
Regards!
I want to temporarily use your function to disable the new cookie security, to allow me to get Coppermine updated - I can see the checkbox "Use basic cookie authentication" but its disabled ?
Keep up the good work team, and thanks for the support so far.
Indeed - the new cookie stuff seems to have disabled TapaTalk access. How is this new authentication checkbox controlled?
You can directly add it to your Settings.php though to bypass this:
$cookie_no_auth_secret = true;
You will be logged out again after changing this.
I added the code to Settings.php but the 'Use basic cookie authentication' checkbox remained greyed out
The only way I could get back into my forum was to manually edit Settings.php and remove/comment out the line $cookie_no_auth_secret = 1;.
Edit: On another forum enabling this setting did not cause any issues as far as logging into SMF was concerned but it didn't resolve the Coppermine bridging issue ...
Regarding the Coppermine bridge. There's two new bridge files you can download to resolve this, uploaded tonight. One for Coppermine 1.5.x https://forum.coppermine-gallery.net/index.php/topic,80028.msg387612.html#msg387612
and one for Coppermine 1.6.x https://forum.coppermine-gallery.net/index.php/topic,77951.msg387613.html#msg387613
No effect, I could not log in (at least with a secondary account) I had to comment on the entire line to allow me to enter ... I would have to do tests with a new user if the same happens but only applies to old users.
Regards!
In the meantime, if manually adding $cookie_no_auth_secret = 1; to your Settings.php isn't enough to make this work as you want, try also adding an entry for 'integrate_verify_user' to the settings table in your database, and give it a dummy value, as shown in the attached image.