summaryrefslogtreecommitdiff
path: root/UPGRADING
diff options
context:
space:
mode:
authorDamien Miller <djm@mindrot.org>2000-01-03 20:00:52 +1100
committerDamien Miller <djm@mindrot.org>2000-01-03 20:00:52 +1100
commite9c8f4dfdc0117fb02b9d9a421f07464ccadfcff (patch)
tree913ab445f121847b23814d849ce74c23facbda27 /UPGRADING
parent645c598d3c6c64f1f20de6fc43d4484033417b4d (diff)
- Removed "nullok" directive from default PAM configuration files.
Added information on enabling EmptyPasswords on openssh+PAM in UPGRADING file.
Diffstat (limited to 'UPGRADING')
-rw-r--r--UPGRADING21
1 files changed, 21 insertions, 0 deletions
diff --git a/UPGRADING b/UPGRADING
index 56585de4..6350fe04 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -57,3 +57,24 @@ If it annoys you too much, set "PermitEmptyPasswords no" in
sshd_config. This will quiet the error message at the expense of
disabling logins to accounts with no password set. This is the
default if you use the supplied sshd_config file.
+
+6. Empty passwords not allowed with PAM authentication
+
+To enable empty passwords with a version of OpenSSH built with PAM you
+must add the flag "nullok" to the end of the password checking module
+in the /etc/pam.d/sshd file. For example:
+
+auth required/lib/security/pam_unix.so shadow nodelay nullok
+
+This must be done in addtion to setting "PermitEmptyPasswords yes"
+in the sshd_config file.
+
+There is one caveat when using empty passwords with PAM
+authentication: PAM will allow _any_ password when authenticating
+an account with an empty password. This breaks the check that sshd
+uses to determined whether an account has no password set and grant
+users access to the account regardless of the policy specified by
+"PermitEmptyPasswords". For this reason, it is recommended that you do
+not add the "nullok" directive to your PAM configuration file unless
+you specifically wish to allow empty passwords.
+