Quote:
Originally Posted by GeorgeYellow
So I think I understand parts of this, from your description.
There are cached entries in
Code:
.active_content_sandbox/store/resource/LocalStorage/https_www.amazon.com_0.localstorage
To actually use try this you need a special captive portal.
It needs to answer
Code:
/kindle-wifi/wifistub-eink.html
with an HTML file that contains the magic string
Code:
81ce4465-7167-4dcb-835b-dcc9e44c112a
.
Everything else is ignored.
If you don't have this string, it triggers captive portal detection, and you can't actually access the store.
However, with all this, I've only gotten to replace the store a handful of times..
1. There seems to be another cache (?), so the only sure way to see an update is to reboot!?!
2. Each time, I've found I need to update the cache times (to be later than the internal cache)
3. I wasn't able to inject pages that aren't elsewhere - eg, I can't add the KU advertisement page ("/kindle-dbs/hz/subscribe/ku" ) - but it still displays top bar
4. Webkit seems to be very sensitive to errors - if there's a javascript error, you see nothing?
Aside from the caching and the rebooting, you know Amazon is going to fix the "bouncing on the \"bed\" " bug. |
Interesting method, Mesquito, as I'm calling it does not utilise the captive portal, this is an interesting method though.
I am aware that Amazon can, and will probably fix it withing weeks, or even days of release, but as it is literally NOT a security threat in my opinion it would only be spiting the community
Mesquito itself has safeguards for a lot of the issues with direct cache replacement
