Quote:
Originally Posted by mr.w0lf
I'm a bit tired so maybe I am saying something (more) stupid (than usual)..
|
Ummm.... I'm afraid that you're right
Quote:
Originally Posted by mr.w0lf
Amazon removed nativeBridge.dbgCmd, but why not find out how it was working and making a sobstitute for it, maybe giving the user the choice if allow root access or not? (like superuser on android)
|
This was previously working precisely because there was functionality inside a system application (wafapp IIRC, but don't quote me on that; it may have been a library as well) which deliberately allowed to break out of "protected" javascript mode into native mode. This is commonly known as a "security hole", and the mechanism is commonly known as an "exploit". Amazon has closed the security hole so that this exploit is no longer possible.
Of course, you can write a substitute for this. You can even replace the entire webkit library. Or the Operating system.
The real challenge is to write something that allows you to perform additional functionality (ideally) on an unmodified device, or (second choice) that works on a modified device, while still not causing problems on an unmodified one.
If you're serious about this, then I suggest to take a look at the waf application and libraries, followed by the LIPC mechanisms.