问题原文
原帖链接 · user40974 · CC BY-SA 3.0
Let's assume the following. We have a server which is accessible via SSH. There is an user in /etc/passwd who has a valid login shell (so for example /bin/bash, instead of an invalid one like /bin/false).
This user has an asterisk (*) in the second (password) field of /etc/shadow. Is there some way that this user could login via SSH if he doesn't have a ssh key in his ~/.ssh/ folder?
Or, to rephrase the question somewhat: What would be the reason for many online guides to recommend to disable the login shell, when there is a * in the password field of /etc/shadow?
已采纳解答
原帖链接 · HBruijn · CC BY-SA 4.0
A * in the location of the hashed password in /etc/shadow effectively disables all password based logins as no user input will ever result in a hash value of *. But the user can still login with his/her ssh keys.
Comparing to * the exclamation mark ! is not only an illegal hash but it also traditionally indicates a locked account. OpenSSH in the Portable variant (which is what you have on GNU/Linux) honors locking by ! but only when not using PAM (UsePAM no). Linux PAM's pam_unix module treats * and ! the same way.
Note that different UNIX-like platforms may use another string to lock an account.
The reason to set an invalid shell is simply to prevent interactive login sessions from working (regardless of whether of not a password for the account is set) and will block sudo su - user and similar from working.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
