Inspecting Content of Add-on BIN File

Have a look at this thread:

viewtopic.php?f=19&t=22957&p=126085#p126172

-Dave

a simple tar xvf addons.bin should work except for jedi's add-ons

super-poussin wrote:
a simple tar xvf addons.bin should work except for jedi's add-ons

tar xvf addons.bin shouldn't work because of the index text concatenated at the start of the tar archive.

I followed the thread referenced by Dave and came up with the following command which is essentially what I was doing manually; unfortunately with the same result.

tail -c `head -n 1 EnableRootSSH_1.0-x86.bin | awk -Fsize= '{print $2}' | cut -d, -f1` EnableRootSSH_1.0-x86.bin | tar -xv 
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I've tried to untar the extracted archive under Linux (Fedora), cygwin(Windows), and on the ReadyNAS box itself. All with the same result.

Can someone who has used the SDK to successfully build an addon try reversing the process perhaps?

THANKS
Peter

the tail -c .... will works with add-ons done with the SDK not with jedi's add-ons

the tar xv wv will work on sparc with add-ons done with the SDK not with jedi's add-ons

Skywalker:/tmp# tail -c `head -n 1 /Develop/TRANSMISSION-L/PRO-Transmission_1.73b01Light.bin | awk -Fsize= '{print $2}' | cut -d, -f1` /Develop/TRANSMISSION-L/PRO-Transmission_1.73b01Light.bin | tar -xv

install.sh remove.sh addons.conf files.tgz

Skywalker:/tmp# ls addons errors_003.log fuppes settings.json addons.conf errors_004.log group.4071 toto broken-out errors_005.log install.sh toto.sh e4defrag errors_006.log kmotion_bash vbox.0 e4defrag.c errors_007.log netatalk22053 vbox.1 edimax_jpeg.jpg files.tgz netatalk2994 vbox.2 errors_001.log Fix_Firefox3_0.1.bin netatalk4260 errors_002.log fsck.log remove.sh

Thanks everyone; that's all clear now and my unpack script works as expected for addons created with the SDK.

I originally embarked on this exercise to review what the FixCronEmails_1.0-x86.bin addon was going to do. Subsequently tried to look at a couple of other addons. Unfortunately all the examples I chose were Jedi prepared ones.

Is there a way to unpack Jedi addons or are they being deliberately protected? Don't need to do this, just curious.

THANKS

..or are they being deliberately protected?

yes :)

But with some imagination you can get the hwdecrypt / hwcp bin files deleted during initrd on your NAS.

All you need is ssh root access and a bit of imagination.

(just remember that theses binaries are deleted during boot... and try to find a way to make a backup of things deleted...)

With this binaries you can decrypt bin and firmware (excepted initrd part because it's not the same process, but still doable)

how are bin files extracted on the ReadyNAS? when I install an addon, something is reading the .bin and pulling out all the included files. What program does that?

No specific program, the FrontView module is doing the extraction/installation. Basically doing an untar, then executing install.sh.

The frontview module is some kind of binary executable or something then I presume. It has to strip the header line before untarring it. Anyway, I was able to use the little script mentioned earlier in this thread and it worked fine to inspect a few bins. thanks!