PlannedOsStructure

From Gen4Wiki

[edit] Modify the /, leave the /boot

Since it appears that the kernel and the boot loader are located on a ROM chip, and we do not know if we can even write to this chip, it may be best to crack the Archos digital signature. If the signature is cracked, we can place our own cramfs files into the Archos. This would be the most involved 'OS Structure', but it would give the greatest control.

[edit] alternative

I'd rather propose to leave the whole system in tact and simply find a backdoor by using an exploit against the running system. At best this will allow us to run own applications instantly. No need to break very very long RSA signatures or whatsoever (breaking the signature itself is very unlikely - at best). --Dm8tbr 13:34, 2 April 2007 (CEST)

[edit] new ideas

Oh, look I was right! ;-)

My current idea after being able to ssh into the 605F is to kill the avos_helper.sh and let it restart into a chroot environment where we have write access. This is quite easy I was already able to create a file containing a ext3 filesystem, loop mount it and copy most of the filesystem and "mount -o bind" the other directories into it. The only thing missing at the moment is a chroot binary.

Actually simply hijacking /opt might also be an interesting option for now as pointed out by SideWays on the archosfans forum.

If we get this going we could e.g. exchange the apdf binary for a qt app of our choice. e.g. a recent qtopia build or some maemo or other environment -> "t3h win!"

--Dm8tbr 21:58, 1 January 2008 (CET)