3 Proven Methods to Lock and Unlock Users in Linux

Written by

Reviewed by

Last updated: August 1, 2023

Expert verified

SVG Image


To lock and unlock users in Linux, you can try the following methods:

  1. passwd Command: A quick and simple method to lock and unlock user accounts by disabling/enabling passwords using passwd --lock and passwd --unlock commands, respectively.
  2. usermod Command: Offers more flexibility, allowing account locking by setting expiration dates with usermod --expiredate, and reactivation by removing expiration using usermod --expiredate.
  3. /etc/shadow File Manually: Provides ultimate control by manually editing the /etc/shadow file to lock an account with an asterisk (*) and unlock by removing it. 

Locking and unlocking user accounts in Linux enhances security and enables efficient user management. Reasons to learn include improved security, easy account reactivation, temporary suspension for investigations, and controlled access to resources. Common errors to avoid are incorrect command syntax, inadequate privileges, failure to set expiration dates, and lack of monitoring and auditing.

Discover different methods to lock and unlock users in Linux in the guide below. Also learn the common errors and the reasons to lock and unlock users.

User management is a crucial aspect of Linux system administration. Ensuring the right users have access to the right resources is fundamental for system security and data protection. Locking and unlocking user accounts in Linux enhances security, streamlines user management, and minimizes vulnerabilities. It ensures accountability, compliance, and smoother operations, reinforcing the system’s resilience against cyber threats. In this comprehensive tutorial, I will explore different methods to lock and unlock users in Linux. I will also discuss common errors and reasons to lock and unlock users.

How to Lock and Unlock Users in Linux

To lock and unlock users in Linux, you have three methods at your disposal. First, the passwd command provides a straightforward way to disable and enable user passwords. Second, the usermod command offers more flexibility, allowing account locking by setting expiration dates and reactivation by removing the expiration. Finally, manually editing the /etc/shadow file provides ultimate control over user accounts, but it’s best suited for experienced users due to potential risks.

1. passwd Command

The passwd command is a straightforward method to lock and unlock users in Linux. It allows you to quickly disable a user’s password to lock their account and later reactivate it by setting a new password. Here’s how you can use it:

  1. Open a Terminal.
opening terminal 4
  1. Run the following command, replacing username with the target user’s username:
<strong>sudo passwd --lock username</strong>
  1. This will disable the user’s password, effectively locking the account.
locking a user account using passwd command
  1. It will now show that the user account is not listed which means it is locked:
user account is locked
  1. To unlock the user account, use the following command:
<strong>sudo passwd --unlock username</strong>
  1. The user can now log in with their password again.
unlocking user account using passwd command
  1. After unlocking the account, it will be listed again:
user account is unlocked

2. usermod Command

The usermod command offers more flexibility in user management, including locking and unlocking accounts by setting expiration dates. This method is ideal for fine-tuning user access and managing temporary suspensions. Follow these steps:

  1. Access your command window.
  2. To lock the user account, execute the following command, replacing username with the target user’s username:
<strong>sudo usermod --expiredate 1 username</strong>
  1. This sets the account’s expiration date to one day ago, effectively locking it.
locking a user account using usermod command 1
  1. Now it will show that the user account is expired when you try to log in the account:
user account is expired
  1. To unlock the user account, use the following command:
<strong>sudo usermod --expiredate "" username</strong>
  1. Removing the expiration date reactivates the account.
unlocking user account using usermod command

3. /etc/shadow File Manually

Manually editing the “/etc/shadow” file provides ultimate control over user account locking and unlocking. However, this method is not recommended for inexperienced users due to potential risks involved in editing system files directly. Here is the step-by-step guide to it:

  1. Open a Terminal as the root user.
  2. Use a text editor such as nano or vim to open the /etc/shadow file:
<strong>sudo nano /etc/shadow</strong>
  1. The command will open the file in nano editor.
opening etc shadow file in nano editor
  1. Locate the line corresponding to the user you want to lock and replace the password field with an asterisk (*):
  1. Save the changes and exit the text editor.
locking user by editing etc shadow file
  1. Now if you try to log in, then it will show the error message “Sorry password authentication didn’t work. Please try again”
password authentication didn t work
  1. To unlock the user account, simply remove the asterisk (*) from the password field and save the changes.
unlocking user by editing etc shadow file
  1. While manually editing the /etc/shadow file provides ultimate control, it is not recommended for novice users due to the potential risks involved.

4 Reasons to Lock and Unlock Users in Linux

Managing user accounts is crucial for maintaining a secure and efficient Linux system. Locking and unlocking user accounts serve distinct purposes, providing sysadmins with a powerful mechanism to control access and enhance security. Here are four reasons why you should learn to lock and unlock users in Linux:

  • 🔒Enhanced Security: Locking user accounts is a proactive measure against potential security breaches. When users leave their accounts idle or inactive for an extended period, locking them prevents unauthorized access and minimizes the risk of intrusions. Similarly, in response to security incidents, temporarily locking compromised accounts halts malicious activities, safeguarding sensitive data and system integrity.
  • 🔓 Account Reactivation: Unlocking user accounts is essential for restoring normal user access after resolving security incidents or addressing other issues. When a user’s account is locked due to inactivity or any other reason, unlocking it allows the user to resume their regular tasks without the need to recreate the account, streamlining user management processes.
  • Temporary Suspension: Temporarily locking user accounts can be necessary during investigations or disciplinary actions. By locking an account, sysadmins can restrict user access temporarily, ensuring that any ongoing inquiries proceed smoothly and security is maintained.
  • 🔑 Controlled Access: Unlocking accounts provides users with authorized access to resources and services, allowing them to perform their assigned tasks efficiently. Controlled access ensures that users with valid credentials can log in and use the system as intended, improving productivity while upholding security measures.

4 Errors When Locking and Unlocking User Accounts in Linux

While locking and unlocking user accounts are essential tasks for system administrators, errors in the process can lead to security vulnerabilities and operational challenges. Understanding these common errors is crucial to ensure a smooth and secure user management experience. Here are four common errors:

  • 🔒 Incorrect Command Syntax: One of the most common errors occurs when administrators use the wrong command syntax to lock or unlock user accounts. A misplaced character or misspelled command can result in unintended consequences, such as accidental account deactivation or reactivation.
  • Inadequate Privileges: Insufficient administrative privileges can prevent sysadmins from effectively locking or unlocking user accounts. Without the necessary permissions, attempts to modify user accounts may be rejected, impeding the intended actions.
  • 🚫 Failure to Set Expiration Dates: When manually locking user accounts by setting expiration dates, administrators may forget to specify the correct date or omit the expiration altogether. This oversight can result in accounts remaining locked indefinitely or unlocking prematurely, leading to security gaps.
  • ⚠️ Lack of Monitoring and Auditing: Failing to monitor and audit user account locking and unlocking activities can hinder the detection of unauthorized actions or security breaches. Without comprehensive logging, administrators may miss crucial insights into account management activities, compromising overall system security.

In A Nutshell

I’ve provided you with comprehensive insights into the methods to lock and unlock users in Linux, empowering you to enhance system security and streamline user management. Be cautious of common errors that can occur, such as incorrect command syntax and inadequate privileges, and remember the reasons to lock and unlock users: bolstering security, minimizing vulnerabilities, and maintaining compliance.

As you continue your journey in Linux system administration, I encourage you to explore further topics to expand your expertise. Explore articles on securing SSH access, implementing two-factor authentication, and Linux firewall configurations and data encryption techniques. The world of Linux administration is vast and ever-evolving, so keep learning and exploring to stay at the forefront of securing your system and mastering the art of user management.

Frequently Asked Questions

How can I monitor user account activity to detect suspicious behavior?

To monitor user account activity and detect suspicious behavior, you can utilize tools like auditd, which is a comprehensive auditing framework available on Linux systems. auditd allows you to track system events, including user logins, file access, and administrative actions. By setting up auditing rules and monitoring the generated audit logs, you can identify unusual patterns, unauthorized access attempts, or potential security breaches. Regularly reviewing audit logs enables system administrators to promptly respond to security incidents, maintain accountability, and ensure the integrity of the system.

Are there any security implications of unlocking a user account remotely?

Unlocking a user account remotely can indeed present security implications if done without proper authentication and authorization. When unlocking an account remotely, there is a risk of unauthorized access if the authentication process is compromised. Malicious actors may attempt to gain unauthorized access to the system by exploiting vulnerabilities in the remote unlocking mechanism. To mitigate these risks, it is crucial to implement strong authentication mechanisms, such as two-factor authentication (2FA), and limit the scope of users who have the authority to remotely unlock accounts. Additionally, monitoring and logging remote unlocking activities can help detect and respond to any suspicious or unauthorized actions promptly.

In the case of forgotten user passwords, the recommended procedure is to utilize the passwd command’s password reset functionality. As a system administrator, you can facilitate this process for users by using the passwd command with the appropriate options to allow them to reset their passwords securely. Upon execution, the command prompts users to enter a new password, ensuring that they regain access to their account while maintaining security. Encourage users to choose strong and unique passwords to enhance overall system security. By providing this self-service password reset feature, you reduce the administrative burden and empower users to manage their own accounts responsibly.



Ojash is a skilled Linux expert and tech writer with over a decade of experience. He has extensive knowledge of Linux's file system, command-line interface, and software installations. Ojash is also an expert in shell scripting and automation, with experience in Bash, Python, and Perl. He has published numerous articles on Linux in various online publications, making him a valuable resource for both seasoned Linux users and beginners. Ojash is also an active member of the Linux community and participates in Linux forums.



Akshat is a software engineer, product designer and the co-founder of Scrutify. He's an experienced Linux professional and the senior editor of this blog. He is also an open-source contributor to many projects on Github and has written several technical guides on Linux. Apart from that, he’s also actively sharing his ideas and tutorials on Medium and Attirer. As the editor of this blog, Akshat brings his wealth of knowledge and experience to provide readers with valuable insights and advice on a wide range of Linux-related topics.

Share this article
Shareable URL
Prev Post

How to Use Paste Command in Linux [4 Best Uses]

Next Post

How To Remove APT Repository In Ubuntu [4 Best Methods]

Leave a Reply

Your email address will not be published. Required fields are marked *

Read next