Quote:
Originally Posted by hfpop
I am interested to block the call-home "feature" of Kindle (I mean, not sending the logs). Is BBB the right thing to do, or this is too much, and simply editing /usr/bin/showlog is enough?
A non-related question, does the kindle distro have the patch binary? If yes, it is not in the path.
Thank you for the support.
|
Editing /usr/bin/showlog :
- Modifies a file in the Amazon image.
- Will only effect sending of logs, not other data mining.
So that is sort of up to the end-user, if that is sufficiently "private".
In contrast:
- The KUAL firewall introduces a structured set of filter chains.
- The BBB filter itself may be disabled "by button".
- Firewall and BBB filter rules are in USB storage, may be edited by end-user if desired. No changes made in the Amazon image files.
- Opening in-bound access to a service may be easily automated. The rule is always *added* as rule #1 in the appropriate chain and *removed* by an "exact match" delete command.
(No button(s) for the common services in the current release.)
- The "report" functions of counter clearing and reporting works on both the KUAL.firewall and the stock Amazon firewall.
- User can revert to the stock Amazon firewall with a button (no restart required - heck, you can even leave the TCP/IP connections up
).
I like the additional feature set that the KUAL firewall brings to the system. Ah, but I am biased, I wrote it.
Three known "problems" with the current release:
- Does not use the 'reject' target when dropping packets.
- Must be re-activated by the end-user after any "cold start" (full re-boot) of the kernel. Which, for a normal end-user, is rare.
- Seems to interfere with certain Wifi security protocols, even when using a personal, private, access point.
I am not ignoring those things, it is just that I am on semi-holiday from Kindle Hacking this summer.
