Hi, in passwd, what is the meaning of ! (in the password field)? And why, by default, some daemon account (ftp) is disabled (*-ed), but others (sshd, postgres) is !-ed? TIA. Verdi -- +++ GMX - die erste Adresse für Mail, Message, More +++ Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
On Thu, Jan 15, Verdi March wrote:
Hi, in passwd, what is the meaning of ! (in the password field)? And why, by default, some daemon account (ftp) is disabled (*-ed), but others (sshd, postgres) is !-ed?
There is no difference. ! has the same meaning as *. Depends on, which tools at which time created the account. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
Hi, Thorsten Kukuk schrieb:
On Thu, Jan 15, Verdi March wrote:
in passwd, what is the meaning of ! (in the password field)? And why, by default, some daemon account (ftp) is disabled (*-ed), but others (sshd, postgres) is !-ed?
There is no difference. ! has the same meaning as *. Depends on, which tools at which time created the account.
In case of a !, you could unlock that account with usermod -U. I often looked for explanations in the net to understand the !, !!, and * as well as the use of /bin/bash (or other) and /bin/false. Unfortunately I still haven't understood completely. For su to a user, what are the preconditions? And for FTP? And using /bin/false, isn't this still to dangerous to prevent a user from login in? Ré -- Registered Linux User #324404
On Thu, Jan 15, René Matthäi wrote:
Hi,
Thorsten Kukuk schrieb:
On Thu, Jan 15, Verdi March wrote:
in passwd, what is the meaning of ! (in the password field)? And why, by default, some daemon account (ftp) is disabled (*-ed), but others (sshd, postgres) is !-ed?
There is no difference. ! has the same meaning as *. Depends on, which tools at which time created the account.
In case of a !, you could unlock that account with usermod -U.
Not always. Not all implementations allow to unlock an account, which would have an empty password afterwards. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
participants (3)
-
René Matthäi -
Thorsten Kukuk -
Verdi March