PHP permanent login, remember me function implementation methods and safety practices

PHP permanent login, remember me function implementation methods and safety practices_PHP tutorial

WBOY

Release： 2016-07-13 09:55:55

Original

920 people have browsed it

PHP permanent login, remember me function implementation methods and safety practices

　 PHP permanent login, remember me function implementation methods and safety practices

This article mainly introduces the implementation methods and security practices of PHP permanent login and remember me functions. This article focuses on using the database to achieve more secure permanent login and remember me functions. Friends who need it can refer to it

Permanent login refers to a mechanism for continuous authentication between browser sessions. In other words, a user who is logged in today will still be logged in tomorrow, even if user sessions expire between visits. The presence of persistent logins reduces the security of your authentication mechanism, but it increases usability. Instead of troublesome users to authenticate each time they visit, provide the option to remember the login.

From what I have observed, the most common flawed permanent login scheme is to save the username and password in a cookie. The temptation to do this is understandable - instead of prompting the user for a username and password, you can simply read them from the cookie. The rest of the verification process is exactly the same as a normal login, so this scenario is a simple one.

However, if you do store your username and password in cookies, please turn off this feature immediately and read the rest of this section to find some ideas for implementing a more secure solution. You will also need to require all users who use this cookie to change their passwords in the future because their authentication information has been exposed.

Permanent login requires a permanent login cookie, often called an authentication cookie, because cookies are the only standard mechanism used to provide stable data across multiple sessions. If the cookie provides permanent access, it poses a serious risk to the security of your application, so you need to make sure that the data you save in the cookie can only be used for authentication for a limited period of time.

The first step is to devise a method to mitigate the risk posed by captured persistent login cookies. While cookie capture is something you want to avoid, having a defense-in-depth process is best, especially since this mechanism can make your validation form less secure even when everything is working fine. In this way, the cookie cannot be generated based on any information that provides a permanent login, such as the user's password.

To avoid using the user’s password, you can create an identity that is only valid for one-time verification:

The code is as follows:

$token = md5(uniqid(rand(), TRUE));

You can save it in the user's session to associate it with a specific user, but this doesn't help you stay logged in across multiple sessions, which is a big deal. Therefore, you must use a different method to associate this identity with a specific user.

Since the username is less sensitive than the password, you can store it in a cookie, which can help the verification process to confirm which user ID is provided. However, a better approach is to use a secondary identity that is difficult to guess and discover. Consider adding three fields to the data table that stores usernames and passwords: a second identity (identifier), a permanent login identification (token), and a permanent login timeout (timeout).

The code is as follows:

mysql> DESCRIBE users;

　 ------------ ------------------ ------ ----- ------ --- -------

　 ------------ ------------------ ------ ----- ------ --- -------

　 ------------ ------------------ ------ ----- ------ --- -------

By generating and saving a secondary identity and permanent login identity, you can create a cookie that does not contain any user authentication information.

The code is as follows:

　$salt = 'SHIFLETT';

$identifier = md5($salt . md5($username . $salt));

$token = md5(uniqid(rand(), TRUE));

　$timeout = time() 60 * 60 * 24 * 7;

setcookie('auth', "$identifier:$token", $timeout);

When a user uses a permanent login cookie, you can check whether it meets several criteria:

The code is as follows:

　/* mysql_connect() */

　/* mysql_select_db() */

　$clean = array();

　$mysql = array();