Set an administrator password and regular user during installation.
Avoid guessable default credentials.
Which policy is appropriate?
Use strong, unique credentials from installation onward and store them safely. Grant administrative access only where needed.
Detailed explanation
Incorrect. A short shared password is easy to guess and compromises every account.
Correct. Use strong individual credentials and protect them in a secure location.
Incorrect. An installation filename is predictable and not a password.
Incorrect. Empty passwords remove authentication protection.
Try it yourself
An example you can run in a temporary verification environment.
passwd --status "$(id -un)"Expected result
現在利用者のパスワード状態。秘密値は表示しないKey points
- Unique credentials
- Strong password
- Least privilege
Notes
- Environment: shadow-utils系Linux
- Use a disposable VM or test account when validating installation and SSH behavior.
- Exact command output can vary slightly by distribution and OpenSSH version.
Foundation review
Identify the scope
Installation-time choices establish the initial authentication boundary and should not rely on public or shared values.
Check the side effect
Store credentials in an approved secret-management location and test login without exposing the secret.