View Single Post
Old 05-20-2014, 07:17 PM   #84
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by doctorbook View Post
I tried the patch for version 3.3.0 but it seems that does not work.
At the moment, I cannot find https://api.kobobooks.com in FW 3.3.0 and 3.3.1, but since DNSB evidently sees them, this might just be me.

Edit: DNSB has of course the correct address. The encoding however has changed. Each char is now two bytes. For our purpose, every second byte has to have a value of 0; e.g. h\x00t\x00t\x00p\x00s\x00:\x00/\x00/\x00a\x00p\x00i\x00 instead of https://api. I am in a hurry and cannot write the code myself now. Edit 2: Looking at it again, I think it would be more appropriate to interpret the pattern as \x00h instead of h\x00 and so on, and decrease the offset by one.

Another thought: Couldn't we try to prevent the updating by redirecting the url in the host file, rather than patching the library?

Last edited by tshering; 05-21-2014 at 11:44 AM.
tshering is offline   Reply With Quote