Note : You could also just add a new entry with an empty password and change it afterwards with passwd

to:

Note : You could also just add a new entry with an empty password and change it afterwards with passwd. Don't forget, that /etc/passwd is used and changed by passwd, but /etc/passwd is softlinked to /passwd on each reboot. So copy your /etc/passwd to /passwd after each modification

Note : The instructions in the TomsNetworking? article above refer to copying a known encrypted password from the NSLU2 password file. For example, after you change the default admin password, copy the encrypted result to the root account.

to:

Note : The instructions in the http://www.tomsnetworking.com/Sections-article85.php TomsNetworking article above refer to copying a known encrypted password from the NSLU2 password file. For example, after you change the default admin password, copy the encrypted result to the root account.

If your Linux accounts have MD5-encrypted passwords, that trick won't work. In that case, either of these commands on many systems should generate a valid crypt-encrypted password you can use instead:

Changed lines 11-14 from:

If your Linux accounts have MD5-encrypted passwords, that trick won't work. In that case, either of these commands on many systems should generate a valid crypt-encrypted password you can use instead:
perl -e 'printf "%s\n", crypt("mypassword","na");' openssl passwd -crypt -salt na mypassword

Jim Buzbee's article expects you to be able to come up with a known, crypt-encrypted password from a Linux/Unix passwd file to paste into the passwd file on the NSLU2. If your Linux accounts have MD5-encrypted passwords, that trick won't work. In that case, either of these commands on many systems should generate a valid crypt-encrypted password you can use instead:

to:

Jim Buzbee's article expects you to be able to come up with a known, crypt-encrypted password from a Linux/Unix passwd file to paste into the passwd file on the NSLU2.

Note : The instructions in the TomsNetworking? article above refer to copying a known encrypted password from the NSLU2 password file. For example, after you change the default admin password, copy the encrypted result to the root account.

If your Linux accounts have MD5-encrypted passwords, that trick won't work. In that case, either of these commands on many systems should generate a valid crypt-encrypted password you can use instead:

Jim Buzbee's article expects you to be able to come up with a known, crypt-encrypted password from a Linux/Unix passwd file to paste into the passwd file on the NSLU2. If your Linux accounts have MD5-encrypted passwords, that trick won't work. In that case, either of these commands on many systems should generate a valid crypt-encrypted password you can use instead: