NSLU2-Linux
view · edit · print · history

HowTo.GainTelnetAccessViaTheClassicMethod History

Hide minor edits - Show changes to markup

October 07, 2005, at 09:22 PM by Jonas Piela --
Changed line 20 from:

2nd note: From firmware version R63 on it seems that http:// your NSLU2 ip /Management/telnet.cgi has been modified. (further I have no information how to gain telnet access now ;) )

to:

2nd note: From firmware version R63 on it seems that http://yourNSLU2ip/Management/telnet.cgi has been modified. (further I have no information how to gain telnet access now ;) )

October 07, 2005, at 09:21 PM by Jonas Piela -- changes from R63 on
Changed lines 18-20 from:
hack::0:0:root:/share/hdd/conf:/bin/sh
to:
hack::0:0:root:/share/hdd/conf:/bin/sh

2nd note: From firmware version R63 on it seems that http:// your NSLU2 ip /Management/telnet.cgi has been modified. (further I have no information how to gain telnet access now ;) )

December 05, 2004, at 04:44 AM by tman --
Added line 17:
December 04, 2004, at 05:48 PM by smartin --
Changed line 16 from:

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

December 01, 2004, at 07:49 PM by michaelebrownmindspringcom --
Changed line 7 from:

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.

November 21, 2004, at 12:28 PM by smartin --
Changed line 16 from:

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

November 21, 2004, at 12:27 PM by smartin --
Changed line 17 from:

hack::0:0:root:/share/hdd/conf:/bin/sh

to:
hack::0:0:root:/share/hdd/conf:/bin/sh
November 21, 2004, at 12:24 PM by smartin --
Changed lines 14-17 from:

Here, "na" is a random, two-character salt, and "mypassword" is the password to be encrypted.

to:

Here, "na" is a random, two-character salt, and "mypassword" is the password to be encrypted.

Note : You could also just add a new entry with an empty password and change it afterwards with passwd hack::0:0:root:/share/hdd/conf:/bin/sh

October 03, 2004, at 01:12 PM by tman --
Added line 9:
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
to:
perl -e 'printf "%s\n", crypt("mypassword","na");'
->openssl passwd -crypt -salt na mypassword
October 02, 2004, at 07:20 PM by jbuzbee --
Changed lines 5-10 from:

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:
September 17, 2004, at 02:03 AM by sskennel --
Added lines 4-10:

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:

 perl -e 'printf "%s\n", crypt("mypassword","na");'
openssl passwd -crypt -salt na mypassword

Here, "na" is a random, two-character salt, and "mypassword" is the password to be encrypted.

September 13, 2004, at 06:29 AM by rwhitby --
Changed lines 1-3 from:
to:

To access the NSLU2 via telnet, by mounting the hard disk on another machine which can access an ext2/3 partition, follow these instructions:

http://www.tomsnetworking.com/Sections-article85.php

view · edit · print · history · Last edited by Jonas Piela.
Based on work by Jonas Piela, tman, smartin, michaelebrownmindspringcom, jbuzbee, and sskennel.
Originally by rwhitby.
Page last modified on October 07, 2005, at 09:22 PM