Thread: BackDoorLock hack - prevents silent updates
View Single Post
Old 03-02-2013, 07:13 AM   #69
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by dsmid View Post
I have an idea how to stop pushed updates even on KPW and KT but I can't implement it because I don't have any KPW or KT device.

In case someone wants to give it a try:
  1. First you need otaupd to release DBus service name com.lab126.ota. That's easy: search for com.lab126.ota in the binary and replace it by e.g. com.lab126.pta (rhymes with PITA).
  2. Then code a replacement DBus service that registers name com.lab126.ota for itself. Most of the time it would just pass all calls to com.lab126.pta via DBus but when a suspicious request is detected (one that looks like pushed update), it would just log it instead.
    You can use any DBus stack for that, I prefer QtDBus as it worked OK on Kindle 3 last time I tried.
Why to complicate? Simple sed for single text file will work just fine. There is no need to get original com.lab126.ota out of the way.
eureka is offline   Reply With Quote