The "pts/27 is now locked by password: authentication failure" Error: What it means and how to fix it
The error message "pts/27 is now locked by password: authentication failure" is a common issue that Linux users might encounter when attempting to access their system via SSH. This error message indicates that a specific pseudo-terminal (pts/27 in this case) has been locked due to an incorrect password attempt, preventing further login attempts. This happens when the system's security measures kick in to protect against brute-force attacks.
Understanding the error message
Let's break down the message:
- pts/27: This refers to a pseudo-terminal, a virtual terminal used for remote access. In this case, it indicates that a specific terminal is locked.
- is now locked by password: This means that the specific terminal is locked because too many incorrect password attempts have been made.
- authentication failure: This simply confirms that the attempted login was unsuccessful because the provided password was not correct.
Why does this happen?
This error arises as a security precaution to prevent potential attacks. Linux systems have mechanisms in place to prevent brute-force attacks, where attackers attempt to guess the password by repeatedly entering random combinations. If too many incorrect attempts are made within a short period, the system will lock the specific terminal to thwart further attempts.
How to unlock your terminal and regain access
Here's how you can fix this issue and regain access to your system:
- Wait it out: The most straightforward solution is to wait. Most Linux systems have a default lockout period, usually between 15 to 30 minutes. During this time, no further login attempts will be allowed for the affected terminal. Once the lockout period expires, you can try logging in again with the correct password.
- Use another terminal: If you have access to other terminals on the system, you can try logging in using a different pts. For example, if "pts/27" is locked, try accessing through "pts/28".
- Reset the password: If you are unable to wait for the lockout to expire and cannot access other terminals, you might need to reset the password. This should only be done as a last resort, as resetting the password requires root access and can impact other users if you're working on a shared system.
Tips to prevent this error in the future:
- Use strong passwords: Strong passwords with a combination of uppercase letters, lowercase letters, numbers, and special characters are more difficult to guess and help prevent brute-force attacks.
- Enable two-factor authentication: Two-factor authentication (2FA) adds an extra layer of security by requiring a second verification step, typically a code sent to your phone, in addition to your password.
- Lock your account after inactivity: Set your system to automatically lock your account after a certain period of inactivity. This helps prevent unauthorized access if you step away from your computer.
- Monitor security logs: Regularly check your security logs for suspicious activity. This can help you identify potential attacks early and take appropriate action.
Example of a typical situation:
Let's say you're trying to access your server via SSH. You enter your password multiple times but keep getting the error "pts/27 is now locked by password: authentication failure". This indicates that you've made too many incorrect password attempts, and the system has temporarily locked your access to protect itself.
Conclusion
The "pts/27 is now locked by password: authentication failure" error is a sign that your system's security measures are working. By understanding the error and following the suggested steps, you can regain access to your system and prevent similar issues in the future. Remember to prioritize strong passwords and implement other security measures to keep your system safe from malicious attacks.