Birmingham mumbai

[
 52 
]
The third column of this command's output gives you the actual date of the last 
password change for the user. The fourth column tells us how many days are 
required to pass before the user will be able to change their password again. In this 
example, 
jdoe
 can change the password any time because the minimum number of 
days is set to 
0
. We'll talk about how to set the minimum number of days later on 
in this chapter, but I'll give you a brief explanation of what this refers to. At first, 
it may seem silly to require a user to wait a certain number of days to be able to 
change their password. However, never underestimate the laziness of your users. It's 
quite common for a user, when required to change their password, to change their 
password to satisfy history requirements, only to then just change it back to what 
it was originally. By setting a minimum number of days, you're forcing a waiting 
period in between password changes, making it less convenient for your users to 
cycle back through to their original password.
The fifth column, as you can probably guess, is the maximum number of days that 
can pass between password changes. If you require your users to change their 
passwords every certain number of days, you'll see that in this column. By default, 
this is set to 
99999
 days. That number of days is way beyond the human lifespan, so 
it may as well be infinite.
Continuing with the sixth column, we have the number of days that will elapse before 
the expiration date on which the user is warned that they will soon be required to 
change their password. In the seventh column, we set how many days can pass after 
the password expires, in which case the account will be disabled. With our example 
user, this is not set. Finally, with the eighth column (which is not visible), we can 
see the number of days since the Unix epoch that will elapse before the account is 
disabled (in our case, there's nothing here, so there is no disabled day set). 

---

Chapter 2