Table of Contents
Permanent login" >Permanent login
Home Backend Development PHP Tutorial PHP Security - Permanent Login

PHP Security - Permanent Login

Feb 20, 2017 am 09:41 AM
php Safety



Permanent login

Persistent 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.

Figure 7-2. Attacker gaining unauthorized access by replaying user’s cookies

From what I've 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 persistent 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:

CODE:
 
  <?php
 
  $token = md5(uniqid(rand(), TRUE));
 
  ?>
Copy after login


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 authenticator determine which user ID was 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).

mysql> DESCRIBE users;
 
+------------+------------------+------+-----+---------+-------+
  | Field      | Type             | Null | Key |
Default | Extra |
 
+------------+------------------+------+-----+---------+-------+
  | username   | varchar(25)      |      | PRI |    
    |       |
  | password   | varchar(32)      | YES  |     |
NULL    |       |
  | identifier | varchar(32)      | YES  | MUL |
NULL    |       |
  | token      | varchar(32)      | YES  |     |
NULL    |       |
  | timeout    | int(10) unsigned | YES  |     |
NULL    |       |
 
+------------+------------------+------+-----+---------+-------+
Copy after login


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

CODE:
 
  <?php
 
  $salt = &#39;SHIFLETT&#39;;
 
  $identifier = md5($salt . md5($username .
$salt));
  $token = md5(uniqid(rand(), TRUE));
  $timeout = time() + 60 * 60 * 24 * 7;
 
  setcookie(&#39;auth&#39;, "$identifier:$token",
$timeout);
 
  ?>
Copy after login


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

CODE:
 
 <?php
 
  /* mysql_connect() */
  /* mysql_select_db() */
 
  $clean = array();
  $mysql = array();
 
  $now = time();
  $salt = &#39;SHIFLETT&#39;;
 
  list($identifier, $token) = explode(&#39;:&#39;,
$_COOKIE[&#39;auth&#39;]);
 
  if (ctype_alnum($identifier) &&
ctype_alnum($token))
  {
    $clean[&#39;identifier&#39;] = $identifier;
    $clean[&#39;token&#39;] = $token;
  }
  else
  {
    /* ... */
  }
 
  $mysql[&#39;identifier&#39;] =
mysql_real_escape_string($clean[&#39;identifier&#39;]);
 
  $sql = "SELECT username, token, timeout
          FROM   users
          WHERE  identifier =
&#39;{$mysql[&#39;identifier&#39;]}&#39;";
 
  if ($result = mysql_query($sql))
  {
    if (mysql_num_rows($result))
    {
      $record = mysql_fetch_assoc($result);
 
      if ($clean[&#39;token&#39;] != $record[&#39;token&#39;])
      {
        /* Failed Login (wrong token) */
      }
      elseif ($now > $record[&#39;timeout&#39;])
      {
        /* Failed Login (timeout) */
      }
      elseif ($clean[&#39;identifier&#39;] !=
              md5($salt . md5($record[&#39;username&#39;] .
$salt)))
      {
        /* Failed Login (invalid identifier) */
      }
      else
      {
        /* Successful Login */
      }
 
    }
    else
    {
      /* Failed Login (invalid identifier) */
    }
  }
  else
  {
    /* Error */
  }
 
  ?>
Copy after login


You should adhere to three aspects to limit the use of permanent login cookies.

##l Cookie needs to expire within one week (or less)

l Cookie It is best to only use it for one verification (delete or regenerate after a successful verification)

l Limit the cookie to expire within a week (or less) on the server side

If you want the user to be remembered indefinitely, as long as the user visits your application more frequently than the expiration time, simply regenerate the identifier after each verification and set a new cookie. Can.

另一个有用的原则是在用户执行敏感操作前需要用户提供密码。你只能让永久登录用户访问你的应用中不是特别敏感的功能。在执行一些敏感操作前让用户手工进行验证是不可替代的步骤。

最后,你需要确认登出系统的用户是确实登出了,这包括删除永久登录cookie:

CODE:
 
  <?php
 
  setcookie(&#39;auth&#39;, &#39;DELETED!&#39;, time());
 
  ?>
Copy after login


上例中,cookie被无用的值填充并设为立即过期。这样,即使是由于一个用户的时钟不准而导致cookie保持有效的话,也能保证他有效地退出。

 以上就是PHP安全-永久登录的内容,更多相关内容请关注PHP中文网(www.php.cn)!


Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

AI Hentai Generator

AI Hentai Generator

Generate AI Hentai for free.

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

PHP 8.4 Installation and Upgrade guide for Ubuntu and Debian PHP 8.4 Installation and Upgrade guide for Ubuntu and Debian Dec 24, 2024 pm 04:42 PM

PHP 8.4 brings several new features, security improvements, and performance improvements with healthy amounts of feature deprecations and removals. This guide explains how to install PHP 8.4 or upgrade to PHP 8.4 on Ubuntu, Debian, or their derivati

How To Set Up Visual Studio Code (VS Code) for PHP Development How To Set Up Visual Studio Code (VS Code) for PHP Development Dec 20, 2024 am 11:31 AM

Visual Studio Code, also known as VS Code, is a free source code editor — or integrated development environment (IDE) — available for all major operating systems. With a large collection of extensions for many programming languages, VS Code can be c

7 PHP Functions I Regret I Didn't Know Before 7 PHP Functions I Regret I Didn't Know Before Nov 13, 2024 am 09:42 AM

If you are an experienced PHP developer, you might have the feeling that you’ve been there and done that already.You have developed a significant number of applications, debugged millions of lines of code, and tweaked a bunch of scripts to achieve op

How do you parse and process HTML/XML in PHP? How do you parse and process HTML/XML in PHP? Feb 07, 2025 am 11:57 AM

This tutorial demonstrates how to efficiently process XML documents using PHP. XML (eXtensible Markup Language) is a versatile text-based markup language designed for both human readability and machine parsing. It's commonly used for data storage an

Explain JSON Web Tokens (JWT) and their use case in PHP APIs. Explain JSON Web Tokens (JWT) and their use case in PHP APIs. Apr 05, 2025 am 12:04 AM

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

PHP Program to Count Vowels in a String PHP Program to Count Vowels in a String Feb 07, 2025 pm 12:12 PM

A string is a sequence of characters, including letters, numbers, and symbols. This tutorial will learn how to calculate the number of vowels in a given string in PHP using different methods. The vowels in English are a, e, i, o, u, and they can be uppercase or lowercase. What is a vowel? Vowels are alphabetic characters that represent a specific pronunciation. There are five vowels in English, including uppercase and lowercase: a, e, i, o, u Example 1 Input: String = "Tutorialspoint" Output: 6 explain The vowels in the string "Tutorialspoint" are u, o, i, a, o, i. There are 6 yuan in total

Explain late static binding in PHP (static::). Explain late static binding in PHP (static::). Apr 03, 2025 am 12:04 AM

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

What are PHP magic methods (__construct, __destruct, __call, __get, __set, etc.) and provide use cases? What are PHP magic methods (__construct, __destruct, __call, __get, __set, etc.) and provide use cases? Apr 03, 2025 am 12:03 AM

What are the magic methods of PHP? PHP's magic methods include: 1.\_\_construct, used to initialize objects; 2.\_\_destruct, used to clean up resources; 3.\_\_call, handle non-existent method calls; 4.\_\_get, implement dynamic attribute access; 5.\_\_set, implement dynamic attribute settings. These methods are automatically called in certain situations, improving code flexibility and efficiency.

See all articles