Writing to Protected Directories

[Sothh]

So I have my Kindlet working, but I want to write a file to the "documents" directory. I found out really fast that my PW did not like that idea. At all. java.security.AccessControlException: access denied

So, am I just out of luck, or is there anyway to get around this?

Thanks!

[knc1]

Originally Posted by Sothh

So I have my Kindlet working, but I want to write a file to the "documents" directory. I found out really fast that my PW did not like that idea. At all. java.security.AccessControlException: access denied

So, am I just out of luck, or is there anyway to get around this?

Thanks!

The "Kindlet Jailbreak" modifies the "sandbox" limits that Kindlet's run inside of.

Hmm...
Source is probably in one of ixtab's repositories if not included in the Kindlet Jailbreak archive.

[Sothh]

Found his source, and got it working perfectly. Now I can write to anywhere! The scary part means now I can write a Kindlet to wipe all the data from my Kindle...

A thought and a two questions,

The thought: Because this is possible, I believe the forum should strongly encouraged that Kindlets be released with their source. Otherwise, it would not take very much malicious code to really screw up someone's Kindle.

And the questions: Will the Kindlet Jailbreak allow me to use sockets for networking? And, does the Kindlet Jailbreak work on non-jailbroken devices?

As for the second, I am sure Amazon would quickly revoke any developer that used it for a public release.

Thanks!

[aditya3098]

All devs here release their source. We're not amazon.

[ixtab]

Originally Posted by Sothh

Found his source, and got it working perfectly. Now I can write to anywhere! The scary part means now I can write a Kindlet to wipe all the data from my Kindle...

A thought and a two questions,

The thought: Because this is possible, I believe the forum should strongly encouraged that Kindlets be released with their source. Otherwise, it would not take very much malicious code to really screw up someone's Kindle.

And the questions: Will the Kindlet Jailbreak allow me to use sockets for networking? And, does the Kindlet Jailbreak work on non-jailbroken devices?

As for the second, I am sure Amazon would quickly revoke any developer that used it for a public release.

Thanks!

The "trust" issue is the same everywhere. If you don't trust someone, don't install his/her programs

That said, you can build your own safety net while developing by requesting very specific permissions (e.g., write permissions for a particular directory only, instead of AllPermissions), so you don't accidentally screw up.

Concerning sockets: I never tried, but it should work. You may also need to extend SuicidalKindlet (instead of AbstractKindlet) in order to escape the restricted Kindlet Class Loader - see KUAL, JBPatch, or Collections Manager sources for examples.

To install the Kindlet jailbreak, your device has to be jailbroken in the first place. So no, it won't work on stock FWs.

[knc1]

Originally Posted by Sothh

- - -
The thought: Because this is possible, I believe the forum should strongly encouraged that Kindlets be released with their source. Otherwise, it would not take very much malicious code to really screw up someone's Kindle.
- - -

Originally Posted by aditya3098

All devs here release their source. We're not amazon.

Oh, but we do strongly encourage.
We use something here called: "Peer Pressure". Not a "policy" or "practice" enforced by the site operators.
Which is why you will not find it written in the "Guidelines" page link.

Originally Posted by ixtab

The "trust" issue is the same everywhere. If you don't trust someone, don't install his/her programs

Example:
But I was just surfing the web and found this XYZWX posted here -
Should I trust the posting?

Answer:
Read the thread.
Posted without sources will generate a large number of comment posts requesting that the source be released.
Then, like anywhere else, make up your own mind.

Our history here shows that it (peer pressure) works quite well.
A bit slowly in a very few cases (authors wanted time to "clean up" their code first), but it works.

PS: Three of our most technically knowledgeable developers here are also forum moderators.
But I don't recall anyone's contribution that required it to be moderated into the bit bucket.
(Other than the special case of copyright violations.)