View Single Post
Old 03-01-2012, 11:33 AM   #198
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Unhappy jailbreak package abuse

Quote:
Originally Posted by ixtab View Post
Hmm... then I would argue that the other jailbreaks are not carefully written.
Agreed. With the signed update packages, developers needed enough knowledge to be able to sign them, and would hopefully know to test them carefully. But most importantly, signed updates will not install on the wrong kindle model.

But with the data.tar.gz method, it drops the payload BEFORE any script can execute, potentially damaging what it replaced. This one is so easy that the "script kiddies" have been busy. There are a lot of RUNME.sh payloads out in various threads, packaged with data.tar.gz files for either the touch or the k4nt, and people are installing the wrong ones. I have helped people debrick kindles that had this exact problem. A "not smart" mntus.params payload (like the model-specific ones in the threads) will brick a kindle if it contains the wrong parameter values.

The problem is that the jailbreak packages are being repurposed as a RUNME script launcher, which is so easy to use that the script kiddies are writing versions that are not carefully written (like other typical script-kiddie scripts). There are enough beginners here that the disorganized crossover between k4nt and touch is causing confusion and bricking.
Quote:
Originally Posted by ixtab View Post
(side note: the "reset to english" is a non-issue, because as of now, a non-jailbroken KT cannot have been localized yet, so I'm in fact overwriting the locale file with an identical version; and even if it was, it would be trivial to localize it again).
Actually, the kindle gets localized when you select a language the first time you start it. No jailbreak needed for that. Yes, it would be trivial to change your locale back to your language, but then you would have to explore the menu system -- not as easy for newcomers as the first-time startup language selection.
Quote:
Originally Posted by ixtab View Post
I haven't tested the other jailbreaks, but since the whole purpose of the jailbreak is to install that one key file, I argue that the installers have to clean up after themselves so as to only leave that single file behind. And if they do, then... well, the original uninstaller can be used for either of them
I agree that the purpose of a JAILBREAK is just to install key files. Yifanlu's latest jailbreak also installs the combined developer keys, in addition to the update key. But these jailbreaks also install a payload file (locale in your case, or mntus.params in yifanlu's newer jailbreak package for the k4nt), and more importantly, it runs a RUNME script if it finds one. And this is why the jailbreaks are being used for things OTHER than jailbreak (in fact, installing a jailbreak key in these cases is redundant and incidental, and most script kiddie stuff just replaces the key file installer with their own code). It is usually just the data.tar.gz and its payload that are being packaged with new RUNME scripts to install OTHER things (removal of Special Offers seems to be popular in the forums, but there are a lot of other ones too).

Although data.tar.gz itself is being called a "jailbreak" in various posts, the payload typically does not install a key file, but is being used ONLY to run various RUNME scripts scattered around in the forums (especially in the K4NT threads). Because the locale file only works on the touch, whereas mntus.params works on the k4nt and the touch, when booting diags and when booting main, even yifanlu is using it in his latest jailbreak package (for k4nt).

I use the newer mntus.params payload for my kindle recovery package ("Select Boot" and "Fastboot Manifesto" threads) for touch and k4nt recovery. This payload also works on earlier kindles too, but requires a different delivery mechanism. I was careful to make it a "smart" (aware of its environment) script so it will work on all kindle models (but needs adjusting for k1 and k2).

The purpose of my thread was to clear up some of the misunderstanding, and provide a little history lesson about using the tar bug payloads, and where it is heading. No intentions here to step on any toes...

P.S. I bumped your karma from ~4500 to ~7500 yesterday, so that should take your mind off your sore toes.

Last edited by geekmaster; 03-01-2012 at 12:00 PM.
geekmaster is offline   Reply With Quote