[yifanlu]

Originally Posted by NiLuJe

Update time!

* JailBreak v0.5.N:
* Works on FW 3.1, thanks to yifanlu . But there is a twist. Like I said on the jb thread, it's based on a whitelist of hacks to decide when to switch to our custom key (in order to successfully install a custom hack). You'll find this whitelist in linkjail/etc/whitelist. Right now, I think it covers a whole bunch of hacks, but if for some reason it's missing something (in which case your hack install will fail with a U007 error), here's how to procede:

* Notify me, so I can fix it for everyone .
* Edit the whitelist manually in linkjail/etc/whitelist (the format should be pretty self-explanatory, just make sure it stays with UNIX line endings).
* Alternatively, you can also drop a blank ENABLE_HACK_UPDATES file in the root of your Kindle, like with yifanlu's jailbreak. (As a side-effect, this will make official updates *fail*).

* Fonts V4.3.N:
* Updated FreeType libs (There might be some significant speed/rendering improvements).
* Updated fc-scan binary (fontconfig update)
* Slightly smarter official update 'traps' (it's using the jailbreak whitelist).

* ScreenSavers v0.19.N:
* Updated sort binary (updated coreutils)
* Slightly smarter official update 'traps' (it's using the jailbreak whitelist).

* USBNetwork v0.31.N:
* Updated sftp-server binary (OpenSSH update)
* Updated dropbear binary (dropbear update)
* Updated htop binary (htop update)
* Updated busybox binary (busybox update)
* Updated rsync binary (rsync update)

Nice update. I do not understand the "whitelist" thing though. Let's say I want to install a hack that's on the whitelist. When I copy it to the Kindle, what's letting it know to change keys? I don't see an loop in the linkjail script, or a callback script. If you have to restart for the keychange to take place, why is there a need for a whitelist? Just call otaup's sigcheck function, if it fails, change keys. If you don't need to restart for keychange to take place, can you tell me what's happening?