chage - Minimum number of days between password change
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
is there any difference in the "Minimum number of days between password change" set to -1
and 0
?
or maybe both commas does the same policy?
chage -m -1 user
chage -m 0 user
thank you for any hint, I can't find -1 descirbed in chage manual but it is possible to set it to -1
Minimum number of days between password change : -1
linux centos rhel password
add a comment |Â
up vote
1
down vote
favorite
is there any difference in the "Minimum number of days between password change" set to -1
and 0
?
or maybe both commas does the same policy?
chage -m -1 user
chage -m 0 user
thank you for any hint, I can't find -1 descirbed in chage manual but it is possible to set it to -1
Minimum number of days between password change : -1
linux centos rhel password
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
is there any difference in the "Minimum number of days between password change" set to -1
and 0
?
or maybe both commas does the same policy?
chage -m -1 user
chage -m 0 user
thank you for any hint, I can't find -1 descirbed in chage manual but it is possible to set it to -1
Minimum number of days between password change : -1
linux centos rhel password
is there any difference in the "Minimum number of days between password change" set to -1
and 0
?
or maybe both commas does the same policy?
chage -m -1 user
chage -m 0 user
thank you for any hint, I can't find -1 descirbed in chage manual but it is possible to set it to -1
Minimum number of days between password change : -1
linux centos rhel password
asked Aug 3 at 20:00
Tomek
61
61
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
If you take a look at the source for chage
there's a comment that explains what -1
does:
/*
* new_fields - change the user's password aging information interactively.
*
* prompt the user for all of the password age values. set the fields
* from the user's response, or leave alone if nothing was entered. The
* value (-1) is used to indicate the field should be removed if possible.
* any other negative value is an error. very large positive values will
* be handled elsewhere.
*/
So when you specify chage -m -1 <user>
it's disabling the mindays field. So disabling it with a -1
vs. setting it to 0 would appear to have the same effect, when it comes to restricting the how frequently a user can change their password.
References
- github repo - shadow/src/chage.c
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
If you take a look at the source for chage
there's a comment that explains what -1
does:
/*
* new_fields - change the user's password aging information interactively.
*
* prompt the user for all of the password age values. set the fields
* from the user's response, or leave alone if nothing was entered. The
* value (-1) is used to indicate the field should be removed if possible.
* any other negative value is an error. very large positive values will
* be handled elsewhere.
*/
So when you specify chage -m -1 <user>
it's disabling the mindays field. So disabling it with a -1
vs. setting it to 0 would appear to have the same effect, when it comes to restricting the how frequently a user can change their password.
References
- github repo - shadow/src/chage.c
add a comment |Â
up vote
1
down vote
If you take a look at the source for chage
there's a comment that explains what -1
does:
/*
* new_fields - change the user's password aging information interactively.
*
* prompt the user for all of the password age values. set the fields
* from the user's response, or leave alone if nothing was entered. The
* value (-1) is used to indicate the field should be removed if possible.
* any other negative value is an error. very large positive values will
* be handled elsewhere.
*/
So when you specify chage -m -1 <user>
it's disabling the mindays field. So disabling it with a -1
vs. setting it to 0 would appear to have the same effect, when it comes to restricting the how frequently a user can change their password.
References
- github repo - shadow/src/chage.c
add a comment |Â
up vote
1
down vote
up vote
1
down vote
If you take a look at the source for chage
there's a comment that explains what -1
does:
/*
* new_fields - change the user's password aging information interactively.
*
* prompt the user for all of the password age values. set the fields
* from the user's response, or leave alone if nothing was entered. The
* value (-1) is used to indicate the field should be removed if possible.
* any other negative value is an error. very large positive values will
* be handled elsewhere.
*/
So when you specify chage -m -1 <user>
it's disabling the mindays field. So disabling it with a -1
vs. setting it to 0 would appear to have the same effect, when it comes to restricting the how frequently a user can change their password.
References
- github repo - shadow/src/chage.c
If you take a look at the source for chage
there's a comment that explains what -1
does:
/*
* new_fields - change the user's password aging information interactively.
*
* prompt the user for all of the password age values. set the fields
* from the user's response, or leave alone if nothing was entered. The
* value (-1) is used to indicate the field should be removed if possible.
* any other negative value is an error. very large positive values will
* be handled elsewhere.
*/
So when you specify chage -m -1 <user>
it's disabling the mindays field. So disabling it with a -1
vs. setting it to 0 would appear to have the same effect, when it comes to restricting the how frequently a user can change their password.
References
- github repo - shadow/src/chage.c
edited Aug 4 at 0:39
answered Aug 4 at 0:31
slmâ¦
232k65479648
232k65479648
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460409%2fchage-minimum-number-of-days-between-password-change%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password