i was soo mad my other server couldnt auto-login to this WD device(but worked fine vice-versa) using keys that i matched settings from my other server but am now locked out of ssh for the my book world ii. i had made a backup of the /etc/sshd_config file but its on the server. any way to fix this??
Well I always tell people to make a share that has access to all your config files in case this happens. You could always take out the drives and mount them to a linux box and edit the file there.
i see. i tried to pull the hdd out by the plastic holder and the plastic holder broke. the hdd wouldnt budge with the little space i had to try to pull it out manually. oh well.
Same situation here - is there no working telnet hack anymore? Would be happy to get into the system to reconfigure the sshd_config which is now wrecked. Or then using the hack were a ssh2 demon is installed on the box, but seems that one is not working either nomore…
I clobbered the sshd_config file as well….. I need to access the file to restore a setting. I have mounted (one of) the drives in a separate PC, and am running knoppix. But since knoppix doesn't support RAID directly, I have to run some "mdadm" commands to enable access. I believe this (busybox) linux doesn't use Logical Volumes, so the RAID1 config should be simple, but haven't figured it out yet…..
There is a tutorial on www.howtoforge.com about recovering from RAID 1 on top of Logical volumes…..
if you have a bluering version,
- i have a firmware hack to enable telnet…
or, if you already have feature pack manager installed, i have a debug feature pack to help you solving sshd config …
just let me know if you are interested….
I have a white (new) version. I saw the telnet hack, not there now.
Would it work on the white ring….? Not sure.
I also saw the serial port, but ckt board looks much smaller than one shown. Not sure I want to tear box apart yet :)
Hi, for the whitelight, i have no solution for ssh…
if you have the single drive model, you might check the Mybook Rescue tool … but it is a bit heavy solution for this issue…
or you could try to boot on a linux live cd and check if you can repair the damaged file manually …