


PHP practical tutorial: filtering, verification, escaping and password methods
This article mainly introduces to you the relevant information about filtering, verification, escaping and passwords in PHP practical tutorials. Friends in need can refer to it. Let's take a look together.
1. Filtering, verification and escaping
1). Do not trust any data from data sources that are not under your direct control. Including but not limited to:
$_GET
$_POST
-
$_REQUEST
$_COOKIE
$argv
php://stdin
php://input
file_get_contents()
Remote database
Remote API
Data from client
2). Solution: Filter input. To remove unsafe characters, data must be filtered before it reaches the application's storage layer. The data that needs to be filtered includes but is not limited to: HTML, SQL queries and user profile information.
HTML: Use the
htmlentities()
function to filter HTML into corresponding entities. This function escapes the specified HTML characters for safe rendering at the storage layer. The correct way to use it is to usehtmlentities($input, ENT_QUOTES, 'UTF-8')
to filter input. Or use HTML Purifier. Disadvantage is slowSQL query: Sometimes a SQL query must be constructed based on the data. At this time, you need to use PDO preprocessing statements to filter external data.
User profile information: Use
filter_var()
andfilter_input()
to filter user profile information
3). Verify data: You can also use filter_var()
. Successful verification will return the value to be verified, and failure will return false. But this function cannot verify all data, so some verification function components can be used. For example, aura/filter or symfony/validator
4) Escape output: You can still use the htmlentities function, and some template engines also have their own escape functions.
Password
1). Never know the user’s password.
2). Never restrict the user’s password. If you want to restrict it, only limit it to the minimum length.
3). Never use email to send user passwords. You can send a link to change the password with a token to verify that it is the user.
4). Use bcrypt to calculate the hash value of the user password. Encryption and hashing are not the same thing. Encryption is a two-way algorithm and the encrypted data can be decrypted. However, hashing is a single algorithm, and the data after hashing cannot be restored. The data obtained after hashing the same data is always the same. Use a database to store the value after hashing the password with bcrypt.
5). Use the Password Hash API to simplify the operation of calculating password hashes and verifying passwords. The following are the general operations for registered users
POST /register.php HTTP/1.1 Content-Length: 43 Content-type: application/x-www-form-urlencoded email=xiao@hello.world&password=nihao
The following is the PHP file that accepts this request
<?php try { $email = filter_input(INPUT_POST, 'email', FILTER_VALIDATE_EMAIL); if (!$email) { throw new Exception('Invalid email'); } $password = filter_iput(INPUT_POST, 'password'); if (!$password || mb_strlen($password) < 8) { throw new Exception('Password must contain 8+ characters'); } //创建密码的哈希值 $passwordHash = password_hash( $password, PASSWORD_DEFAULT, ['cost' => 12] ); if ($passwordHash === false) { throw new Exception('Password hash failed'); } //创建用户账户,这里是虚构的代码 $user = new User(); $user->email = $email; $user->password_hash = $passwordHash; $user->save(); header('HTTP/1.1 302 Redirect'); header('Location: /login.php'); } catch (Exception $e) { header('HTTP1.1 400 Bad Request'); echo $e->getMessage(); }
6). Modify the third value of password_hash()
according to the specific computing power of the machine. Calculating the hash value generally takes 0.1s-0.5s.
7). The hash value of the password is stored in a database column of type varchar(255)
.
8). General process for logging in users
POST /login.php HTTP1.1 Content-length: 43 Content-Type: application/x-www-form-urlencoded email=xiao@hello.wordl&pasword=nihao
session_start(); try { $email = filter_input(INPUT_POST, 'email'); $password = filter_iinput(INPUT_POST, 'password'); $user = User::findByEmail($email); if (password_verify($password, $user->password_hash) === false) { throw new Exception(''Invalid password); } //如果需要的话,重新计算密码的哈希值 $currentHasAlgorithm = PASSWORD_DEFAULT; $currentHashOptions = array('cost' => 15); $passwordNeedsRehash = password_needs_rehash( $user->password_hash, $currentHasAlgorithm, $currentHasOptions ); if ($passwordNeedsRehash === true) { $user->password_hash = password_hash( $password, $currentHasAlgorithm, $currentHasOptions ); $user->save(); } $_SESSION['user_logged_in'] = 'yes'; $_SESSION['user_email'] = $email; header('HTTP/1.1 302 Redirect'); header('Location: /user-profile.php'); } catch (Exception) { header('HTTP/1.1 401 Unauthorized'); echo $e->getMessage(); }
9 ). The password hashing API before PHP5.5.0 cannot be used. It is recommended to use the ircmaxell/password-compat component.
Related recommendations:
PHP verificationCode class ValidateCode
php verification code class instance sharing
php verifies whether the entered mobile phone number is legal
##
The above is the detailed content of PHP practical tutorial: filtering, verification, escaping and password methods. For more information, please follow other related articles on the PHP Chinese website!

Effective methods to prevent session fixed attacks include: 1. Regenerate the session ID after the user logs in; 2. Use a secure session ID generation algorithm; 3. Implement the session timeout mechanism; 4. Encrypt session data using HTTPS. These measures can ensure that the application is indestructible when facing session fixed attacks.

Implementing session-free authentication can be achieved by using JSONWebTokens (JWT), a token-based authentication system where all necessary information is stored in the token without server-side session storage. 1) Use JWT to generate and verify tokens, 2) Ensure that HTTPS is used to prevent tokens from being intercepted, 3) Securely store tokens on the client side, 4) Verify tokens on the server side to prevent tampering, 5) Implement token revocation mechanisms, such as using short-term access tokens and long-term refresh tokens.

The security risks of PHP sessions mainly include session hijacking, session fixation, session prediction and session poisoning. 1. Session hijacking can be prevented by using HTTPS and protecting cookies. 2. Session fixation can be avoided by regenerating the session ID before the user logs in. 3. Session prediction needs to ensure the randomness and unpredictability of session IDs. 4. Session poisoning can be prevented by verifying and filtering session data.

To destroy a PHP session, you need to start the session first, then clear the data and destroy the session file. 1. Use session_start() to start the session. 2. Use session_unset() to clear the session data. 3. Finally, use session_destroy() to destroy the session file to ensure data security and resource release.

How to change the default session saving path of PHP? It can be achieved through the following steps: use session_save_path('/var/www/sessions');session_start(); in PHP scripts to set the session saving path. Set session.save_path="/var/www/sessions" in the php.ini file to change the session saving path globally. Use Memcached or Redis to store session data, such as ini_set('session.save_handler','memcached'); ini_set(

TomodifydatainaPHPsession,startthesessionwithsession_start(),thenuse$_SESSIONtoset,modify,orremovevariables.1)Startthesession.2)Setormodifysessionvariablesusing$_SESSION.3)Removevariableswithunset().4)Clearallvariableswithsession_unset().5)Destroythe

Arrays can be stored in PHP sessions. 1. Start the session and use session_start(). 2. Create an array and store it in $_SESSION. 3. Retrieve the array through $_SESSION. 4. Optimize session data to improve performance.

PHP session garbage collection is triggered through a probability mechanism to clean up expired session data. 1) Set the trigger probability and session life cycle in the configuration file; 2) You can use cron tasks to optimize high-load applications; 3) You need to balance the garbage collection frequency and performance to avoid data loss.


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

SublimeText3 English version
Recommended: Win version, supports code prompts!

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

SublimeText3 Chinese version
Chinese version, very easy to use

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function
