


Database in PHP implements more secure permanent login and remember me functions
This article mainly introduces the functions of database in PHP to achieve more secure permanent login and remember me. Friends who are interested can refer to it. I hope it will be helpful to everyone.
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.
From my observation, 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.
But 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:
<?php $token = md5(uniqid(rand(), TRUE)); ?>
You can save it in the user session to associate it with a specific user, but this doesn't help you stay logged in across multiple sessions, which is a major premise. 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 program 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; +------------+------------------+------+-----+---------+-------+ | 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 | | +------------+------------------+------+-----+---------+-------+
By generating and saving a second identity ID and a permanent login ID, you can create a cookie that does not contain any user authentication information.
The code is as follows:
<?php $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:
<?php /* mysql_connect() */ /* mysql_select_db() */ $clean = array(); $mysql = array(); $now = time(); $salt = 'SHIFLETT'; list($identifier, $token) = explode(':', $_COOKIE['auth']); if (ctype_alnum($identifier) && ctype_alnum($token)) { $clean['identifier'] = $identifier; $clean['token'] = $token; } else { /* ... */ } $mysql['identifier'] = mysql_real_escape_string($clean['identifier']); $sql = "SELECT username, token, timeout FROM users WHERE identifier = '{$mysql['identifier']}'"; if ($result = mysql_query($sql)) { if (mysql_num_rows($result)) { $record = mysql_fetch_assoc($result); if ($clean['token'] != $record['token']) { /* Failed Login (wrong token) */ } elseif ($now > $record['timeout']) { /* Failed Login (timeout) */ } elseif ($clean['identifier'] != md5($salt . md5($record['username'] . $salt))) { /* Failed Login (invalid identifier) */ } else { /* Successful Login */ } } else { /* Failed Login (invalid identifier) */ } } else { /* Error */ } ?>
You should insist on limiting the use of permanent login cookies in three aspects.
1.Cookies need to expire within one week (or less)
2.Cookies should only be used for one verification (delete or regenerate after a successful verification)
3. Limit cookie expiration on the server side within a week (or less)
If you want the user to be remembered indefinitely, then as long as the user visits your application more frequently than the expiration time If it is large, simply regenerate the identifier and set a new cookie after each verification.
Another useful principle is to require users to provide a password before performing sensitive operations. You should only allow permanently logged-in users to access features of your app that are not particularly sensitive. Asking users to manually verify before performing some sensitive operations is an irreplaceable step.
Finally, you need to confirm that the user who logged out of the system is indeed logged out, which includes deleting the permanent login cookie:
The code is as follows:
<?php setcookie('auth', 'DELETED!', time()); ?>
In the above example, cookie Filled with useless values and set to expire immediately. This way, even if a user's clock remains inaccurate and the cookie remains valid, he or she is effectively logged out.
Summary: The above is the entire content of this article, I hope it will be helpful to everyone's study.
Related recommendations:
PHP traverses and searches strings
PHP WeChat interface implements QR code generation class
The above is the detailed content of Database in PHP implements more secure permanent login and remember me functions. For more information, please follow other related articles on the PHP Chinese website!

What’s still popular is the ease of use, flexibility and a strong ecosystem. 1) Ease of use and simple syntax make it the first choice for beginners. 2) Closely integrated with web development, excellent interaction with HTTP requests and database. 3) The huge ecosystem provides a wealth of tools and libraries. 4) Active community and open source nature adapts them to new needs and technology trends.

PHP and Python are both high-level programming languages that are widely used in web development, data processing and automation tasks. 1.PHP is often used to build dynamic websites and content management systems, while Python is often used to build web frameworks and data science. 2.PHP uses echo to output content, Python uses print. 3. Both support object-oriented programming, but the syntax and keywords are different. 4. PHP supports weak type conversion, while Python is more stringent. 5. PHP performance optimization includes using OPcache and asynchronous programming, while Python uses cProfile and asynchronous programming.

PHP is mainly procedural programming, but also supports object-oriented programming (OOP); Python supports a variety of paradigms, including OOP, functional and procedural programming. PHP is suitable for web development, and Python is suitable for a variety of applications such as data analysis and machine learning.

PHP originated in 1994 and was developed by RasmusLerdorf. It was originally used to track website visitors and gradually evolved into a server-side scripting language and was widely used in web development. Python was developed by Guidovan Rossum in the late 1980s and was first released in 1991. It emphasizes code readability and simplicity, and is suitable for scientific computing, data analysis and other fields.

PHP is suitable for web development and rapid prototyping, and Python is suitable for data science and machine learning. 1.PHP is used for dynamic web development, with simple syntax and suitable for rapid development. 2. Python has concise syntax, is suitable for multiple fields, and has a strong library ecosystem.

PHP remains important in the modernization process because it supports a large number of websites and applications and adapts to development needs through frameworks. 1.PHP7 improves performance and introduces new features. 2. Modern frameworks such as Laravel, Symfony and CodeIgniter simplify development and improve code quality. 3. Performance optimization and best practices further improve application efficiency.

PHPhassignificantlyimpactedwebdevelopmentandextendsbeyondit.1)ItpowersmajorplatformslikeWordPressandexcelsindatabaseinteractions.2)PHP'sadaptabilityallowsittoscaleforlargeapplicationsusingframeworkslikeLaravel.3)Beyondweb,PHPisusedincommand-linescrip

PHP type prompts to improve code quality and readability. 1) Scalar type tips: Since PHP7.0, basic data types are allowed to be specified in function parameters, such as int, float, etc. 2) Return type prompt: Ensure the consistency of the function return value type. 3) Union type prompt: Since PHP8.0, multiple types are allowed to be specified in function parameters or return values. 4) Nullable type prompt: Allows to include null values and handle functions that may return null values.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

WebStorm Mac version
Useful JavaScript development tools

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Zend Studio 13.0.1
Powerful PHP integrated development environment