You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tweak here forces openssh to use PAM auth for cleartext passwords, and this tweak here causes PAM to allow null passwords through the pam_unix.so auth module.
Unfortunately, out of the box, the Angstrom root user does not have a null password, he has NO password, a subtle difference and the user gets a password authentication issue when trying to log in through ssh with a null password.
This stackexchange question here provides an answer to the problem. (See the update at the bottom of the first answer).
/etc/shadow needs to have the encrypted value for null password saved for the root user. For example:
root:U6aMy0wojraho:13721:0:99999:7:::
When I add this to my /etc/shadow file, I can log in with no problem now through ssh.
The text was updated successfully, but these errors were encountered:
This tweak here forces openssh to use PAM auth for cleartext passwords, and this tweak here causes PAM to allow null passwords through the pam_unix.so auth module.
Unfortunately, out of the box, the Angstrom root user does not have a null password, he has NO password, a subtle difference and the user gets a password authentication issue when trying to log in through ssh with a null password.
This stackexchange question here provides an answer to the problem. (See the update at the bottom of the first answer).
/etc/shadow needs to have the encrypted value for null password saved for the root user. For example:
root:U6aMy0wojraho:13721:0:99999:7:::
When I add this to my /etc/shadow file, I can log in with no problem now through ssh.
The text was updated successfully, but these errors were encountered: