| Summary: | PermitEmptyPasswords ignored | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Frank Beckmann <Frank.Beckmann> | ||||||
| Component: | sshd | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> | ||||||
| Status: | CLOSED WONTFIX | ||||||||
| Severity: | critical | ||||||||
| Priority: | P2 | ||||||||
| Version: | -current | ||||||||
| Hardware: | UltraSPARC | ||||||||
| OS: | Solaris | ||||||||
| Attachments: |
|
||||||||
|
Description
Frank Beckmann
2003-11-06 01:45:36 AEDT
Created attachment 492 [details]
ssh_config
Created attachment 493 [details]
sshd_config
I can't replicate this unless I use PAM and the nullok option in my /etc/pam.d/sshd file. Are you using PAM? Hallo we Use PAM Nov 6 09:44:57 zvadm6 sshd[17967]: Accepted keyboard-interactive/pam for wparling from 10.128.78.228 port 1419 ssh2 under solaris there is only an pam.conf, for ssh we dont make any entry. The ssh works correct when we put something as pass in the /etc/shadow Frank This is intended behaviour. When you have "UsePAM yes" all of the password-related code is bypassed entirely - all of the checks are purely up to the PAM modules. Either turn off PAM authentication or look to your PAM config. I'll mention that UsePAM can bypass PermitEmptyPasswords in the sshd_config file. Mass change of RESOLVED bugs to CLOSED |