greatly appreciate any insight you can provide

I will gladly be of help if you can tell me if you can tell me some more about your config.
Are you able to access the drive as a network disk? Can you access the webpage on it.
Which firmware is it running. Have you hacked the drive before?
Is the NAS getting an IP from a DHCP-server and is it able to go on the Internet without a proxy?

With other words… If a stranger comes in with his laptop, will he be able to go on the Internet by merely plugging in the ethernet cable that's going to your NAS?

 INETDCB=/etc/inetd.conf.bak.`date +%Y%m%d-%H%M` 

Note that I'm using the ‘ key (the one to the left of the 1, not the apostrophe). That will set the backup filename of inetd.conf to inetd.conf.bak.20080619-0905. Then if I run the script more than once, I’ll still be able to get to all previous backup copies of inetd.conf in the future.

Just a thought.

-ET

http://www.chiark.greenend.org.uk/~sgtatham/putty/

Have fun :)

http://<IP-OF-YOUR-MYBOOK>/auth/firmware_upgrade.pl?fwserver=martin.hinner.info/mybook/firmware.php

quoted text

. SLow but it worked. Change some names and passwords arround and cannot move beyond it.
How do I run SSH from Windows Vista or XP?
How do I get to the place where I can start seeing and editing linux files on the WorldBookII?

I have had the same problem :
"Connection refused" after upgrade the firmware from Martin Hinner and reboot.

I let you see a little problem with chmod :

So prefer to use chmod 600 to chmod 640 and don't forget to check permissions

Regards

 This is Very very subtle. My 'MyBook' was connected directly to my laptop, and while my laptop could access the internet , the mybook itself could not! Therfore it could not wget the upgrade script. 

Workaround:
I entered the web interface for my MyBook and manually configured an ip address, but MOST importantly the
DNS server ip addresses from my ISP This was my problem! With hindsight, I could probably have just used the ipaddress for MyWebServerName and probably got the same results.

Chayden thanks for the analysis, and Floris!! Thanks for the script. Kudos!!

I have tried the above, but only get the no firmware page (so according to the above posts,
my world book is not fetching the upgrade script)

On my web server I have two files, in a directory called /mybook.
The first is called latestfw.sh (which is the script above (posted by floris oct 22)
The second file is called list.asp and contains the following

 <a href="http://www.MyWebServerName.com/mybook/latestfw.sh">firmware</a> 

I'm calling this via

 http://MyWorldBookIPAddress/auth/firmware_upgrade.pl?fwserver=www.MyWebServerName.com/mybook 

but I just get the "no firmware available" each time.

I've verified that I can wget both files, so directory/file permissions don't appear to be an issue.

Thanks.

Enjoy making a better hack and a safer one :)

First the enabling of sshd:
There is no need whatsoever for the script to generate the keys and start the sshd daemon. There is already a S29sshd init script in /etc/init.d/. This script checks if sshd is enabled in the /etc/inetd.conf config file. If it finds sshd enabled, it generates the keys when needed and starts the deamon at startup of the MyBook. The only thing the firmware script has to do is uncomment the line "ssh stream tcp nowait root /usr/sbin/sshd sshd -i" in /etc/inetd.conf.

Also, blanking the root password is bad for two reasons: First, the default sshd configuration does not accept a blank password for root on deviced I've seen. So even if the firmware gets the sshd daemon running, a user can connect but not login. Second, the default password is very well known. Just search for the shadow hash on the web: 'root'. The default password from a Busybox shadow file.

I hope I can find some time to write a suitable firmware script.

new reboot … and always connection rufused !!!

If that is the case, I could write a loader to add a user with a preset password for you.

http://mybookworld.wikidot.com/forum/t-19138/auth-firmware-upgrade-pl#post-54700

If it allows you to ssh in, then it suceeded. Just add the inittab or init.d entry to make ssh autorun.
Also change your su password.

wget is performed by the upgrade script and wget should be installed in your worldbook by default.

Do remember to have a std user account created in the webinterface to start.

You may want to crate the home directory for your user or setup your user's home dir and group permissions to your public folder. Add to www-data group I beleive. You will need to manually edit the /etc/passwd and /etc/groups files as the user and group commands are not preinstalled.

Where should we try the wget command?

Try this:
wget -O out "http://martin.hinner.info/mybook/firmware.php/list.asp?type=wdg1nc&fw=01.01.18"

Or you can just browse to the link above and see what it gives.

You are looking for a returned file containing "href="<some URL>"
If it does not get something back, or if it does not have href= then you get the "No new firmware availabe" message.

If you DO get something OK back, then it does a wget on the URL it received, and then executes the resulting returned file AS ROOT. You can see what that is by doing another wget on what you got back in the first step.
If you browsed to the link above, then click on the link it gave back and view the upgrade program.

You can set this up on your own website by setting up two web pages, one of which points to the other like the pattern above, and the other which contains the upgrade script.

What is going on is that there is an existing "update firmware" page in the MyBook, and you can pass it a URL telling it where to get the update. It does a wget to fetch from that URL (appended with /list.asp). Then it takes that result, looks within it for another URL, does a wget on it, stores the result in a file, and executes that file as root.

So basically you create two web pages, one containing the program you want to execute and another pointing to it, and give it to the built-in firmware upgrade page.

In my case, I took the program from Martin Hinner (which is left in /var/upgrade/latestfw.sh) and modified it to log its progress in /shares/internal/PULBLIC so I could see what was going on, which allowed me to solve my problem. I have now successfully upgraded both a 500G and a 1T unit. I will build a small zip file with instructions so anyone can do this themselves when I have time.