04-14-2011, 01:25 PM | #1 |
Connoisseur
Posts: 84
Karma: 26720
Join Date: Mar 2011
Device: Kindle 3 WIFI
|
Disable Kindle Logging - Kindlesec.sh
The results from thorough research of the Kindle's back-end linux system has led us to believe that we have successfully identified the scripts that lab128 wrote for the remote backup of log files.
The files in question: /usr/sbin/syslog-ng - syslog server and logging daemon /usr/sbin/loginfo - pulls specific info from syslog /usr/sbin/tinyrot - rotates log files to be pulled from remote servers /usr/sbin/showlog - specifies which log file to send The bash script simply links all these binaries to /dev/null rendering them useless. I have been using my Kindle 3 with no problems, I am able to email to my device and access the Amazon bookstore. This script will also work with the Kindle 3G, however it remains untested. Requires Jailbroken Kindle with ssh/usbnetwork access. Instructions: 1. Download the files - http://gitbrew.org/kindlesec/ 2. Place kindlesec.sh on your Kindle via USB 3. mntroot rw 4. cd /mnt/us 5. ./kindlesec.sh Enjoy your privacy. If you have found this useful please donate. We are hoping to raise enough to procure the latest Kindle model released with ads. If we can get access to one we will be able to create custom screensaver updates to replace them. Let the research continue! Last edited by dasmoover; 04-14-2011 at 03:11 PM. |
04-14-2011, 02:58 PM | #2 |
BLAM!
Posts: 13,497
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Congratulations! You managed to disable/break official/hack updates (un)installs for everyone you managed to lure into trying this ;D.
Hint: We kinda *need* the otaup script. In the same vein, good luck not running out of space in the sys parts without tinyrot! Last edited by NiLuJe; 04-14-2011 at 03:01 PM. |
Advert | |
|
04-14-2011, 03:10 PM | #3 | ||
Grand Sorcerer
Posts: 28,044
Karma: 199464182
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
1.1. Apply Existing jailbreak 1.2. Gain ssh/telnet access Quote:
|
||
04-14-2011, 03:11 PM | #4 |
Connoisseur
Posts: 84
Karma: 26720
Join Date: Mar 2011
Device: Kindle 3 WIFI
|
NiLuJe: Actually, the logging functionality is disabled entirely, no logs are written to the log partition.
However, I have removed the line that disables otaup. I've been running my kindle for a month with this script now and I have not had one single issue. Furthermore, the script creates a backup of all the bin files, you should look at it. DiapDealer: I figured jailbreak and shell was a given, heh. |
04-15-2011, 12:30 AM | #5 |
BLAM!
Posts: 13,497
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@dasmoover: Right, entirely missed the fact that you squished syslog-ng too, my bad .
As for the otaup script, that's one (slightly bruteforce-ish ^^) way of pleasing the 'no official updates plz' crowd, so you may want to keep that, just make it clear it will *completely* disable the 'Update Your Kindle' feature . Anyway, apologies for the slightly snarky tone of my first message . Last edited by NiLuJe; 04-15-2011 at 12:39 AM. |
Advert | |
|
04-25-2011, 12:55 AM | #6 | |
Wizard
Posts: 1,669
Karma: 2300001
Join Date: Mar 2011
Location: Türkiye
Device: Kindle 5.3.7
|
I execute the script both with putty and terminal of winSCP get an error on both:
Code:
/mnt/us$ ./kindlesec.sh Creating backup of loginfo, tinyrot, otaup, showlog, syslog-ng. mkdir: cannot create directory '/mnt/us/.kindlesec/': File exists cp: cannot create '/mnt/us/.kindlesec/syslog-ng': Operation not permitted cp: cannot create '/mnt/us/.kindlesec/loginfo': Operation not permitted cp: cannot create '/mnt/us/.kindlesec/tinyrot': Operation not permitted cp: cannot create '/mnt/us/.kindlesec/showlog': Operation not permitted Pointing log scripts to /dev/null Quote:
( upto now did this script change "anything" on kindle?, if I couldn't manage to run in proper way, can it harm? ) Edit: Indeed, I couldn't install this properly then on the following restart my Kindle bricked.(I'm not 100% sure about the cause since I tried another one at the same time and it also did not function properly) Thanks to the wonderful CS of Amazon I got a replacement even I said them the cause of the problem. Last edited by thomass; 09-02-2011 at 08:13 AM. |
|
09-02-2011, 03:36 AM | #7 |
bookster
Posts: 28
Karma: 5304
Join Date: Jul 2011
Device: Kindle 3 Wifi+3G
|
Nvm, can be deleted.
Last edited by horizon21; 09-02-2011 at 04:49 AM. |
11-23-2011, 01:34 AM | #8 |
Junior Member
Posts: 3
Karma: 2426
Join Date: Nov 2011
Device: K3
|
Hi there
has anyone tested kindlesec.sh on wifi+3G 3.2.X? At http://gitbrew.org/kindlesec/ it says kindlesec.sh is "Depreciated as of 06/04/11" - is this because it does not disable logging for newer versions? |
11-23-2011, 01:16 PM | #9 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
Last edited by geekmaster; 11-23-2011 at 01:18 PM. |
|
11-24-2011, 12:36 AM | #10 |
Junior Member
Posts: 3
Karma: 2426
Join Date: Nov 2011
Device: K3
|
syslog-ng, loginfo, and tinyrot are in /usr/sbin/, however showlog is in /usr/bin/ so it's clear the script is outdated.
At https://www.mobileread.com/forums/showthread.php?t=51371 I it's suggested to just change $NUMFILES and $ALLFILES in showlog - would this be this sufficient? If so, what was the point with kindlesec.sh? did it disable more logging than actually necessary? Anyone found some other hacks for disabling logs sent to amazon? |
11-24-2011, 07:52 AM | #11 |
Connoisseur
Posts: 79
Karma: 2718
Join Date: Aug 2011
Device: Kindle 3G
|
I don't know WHY it was deprecated. The method they used in their script--of effectively removing all the scripts involved in the logging process (plus even the syslog binary)--is still valid. I have the same setup (with some additional modifications) on one of my kindles, from 3.2.1 to now 3.3 with no problems. Perhaps not having syslog was an issue for some in the hack community... I suppose if you rely on the whole debugOn thing, this would be a problem.
That said, I've run like this with no problems for ages and have had no use for syslog-ng running in the background. (It's an e-reader after all--I'm a linux sysadmin and I see no need for syslog to be running on my kindle.) Note: I only use launchpad, screensaver hack, kaffeine, & kinamp. PS: I was sooo surprised when my 3.2.1 kindle didn't complain at all on the 3.3 update--I didn't roll back any of these changes before trying it. |
11-25-2011, 02:04 AM | #12 |
Junior Member
Posts: 3
Karma: 2426
Join Date: Nov 2011
Device: K3
|
I have changed in the script the location of showlog from /usr/sbin/ to /usr/bin/ and I can confirm that everything went fine.
After that I have installed some other hacks with debugOn and they seem to have worked, so apparently there is no issue with updates after turning logging off. With logging off is it still possible for amazon to read and change stuff locally on your kindle? A couple of (slightly unrelated) questions: - Since all browsing traffic seems to be proxied through a server at amazon how can this be circumvented and connect e.g. through wi-fi directly using your own ISP (without going through the amazon proxy)? - Has anyone found any hacks to connect to wifi and browse without the need to register for an amazon account? |
08-22-2012, 08:33 AM | #13 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Quote:
err this is obviously AMENDED. don't bother trying to backstep it and traceroute to google.com (173.194.34.135), 30 hops max, 38 byte packets 1 BThomehub.home (192.168.1.99) 11.040 ms 96.180 ms 99.431 ms I vis tracerrouted these: They are BT in UK 2 217.32.143.99(217.99.143.99) 19.429 ms 18.378 ms 18.093 ms It goes on... for the vaguely interested. Code:
3 217.99.144.99 (217.99.144.99) 19.132 ms 18.357 ms 18.565 ms 4 213.90.181.99(213.99.181.99) 21.486 ms 20.671 ms 21.172 ms 5 217.99.169.99 (217.99.169.99) 21.015 ms 21.471 ms 21.049 ms 6 217.99.169.99 (217.99.169.199) 21.116 ms 21.850 ms 20.594 ms 7 109.99.251.99 (109.99.251.99) 20.160 ms 109.99.251.99 (109.199.251.99) 20.295 ms 109.199.251.99 (109.199.251.99) 21.697 ms 8 core1-te0-12-0-6.ealing.ukcore.bt.net (109.159.251.99) 27.979 ms core1-te0-4-0-2.ealing.ukcore.bt.net (109.159.251.99) 35.703 ms core2-te0-2-4-0.ilford.ukcore.bt.net (109.159.251.99) 36.531 ms 9 peer1-xe3-3-0.telehouse.ukcore.bt.net (109.159.254.99) 26.137 ms peer1-xe3-0-1.telehouse.ukcore.bt.net (109.159.254.99) 28.722 ms 28.205 ms 10 195.99.126.99 (195.99.126.99) 25.872 ms 195.99.125.25 (195.99.125.99) 26.698 ms 195.99.126.99 (195.99.126.99) 26.966 ms 11 209.85.252.99 (209.85.252.99) 28.604 ms 27.916 ms 31.220 ms 12 209.85.253.99 (209.85.253.99) 28.673 ms 28.813 ms 27.778 ms Code:
13 lhr14s21-in-f7.1e100.net (173.194.34.99) 26.539 ms 27.136 ms 27.058 ms < --- I'm gurgle me... hth |
|
08-22-2012, 09:58 AM | #14 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Well, I guess that is one thing to be said about a national, communications monopoly - its organized.
Takes me twice as long to reach google from here - - But that is an artifact of various telecom companies buying each other out over time. The "closest" google server to here is in the network hub on the grounds of the Dallas/Ft. Worth airport - - The "original" provider of the network I have, has a network hub in the same facility - - The "current" provider of the network I have, has a network hub in St. Louis (corporate headquarters town) - - So a packet to the closest google server goes from here, to the "original" hub at DFW, where it is sent to the current owner's hub in St. Louis, where it is then directed back to the google server at DFW - - Probably to the box on the next shelf of the server rack from where it started. Grumble, grumble, grumble |
12-17-2018, 08:11 AM | #15 |
Wizard
Posts: 1,342
Karma: 4752930
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
|
Is this log disabling safe for current PW3 (5.9.7)?
Last edited by mergen3107; 03-24-2020 at 04:41 AM. |
Tags |
logging, logs |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Hacks Kindle DX - Any way to disable screensaver? | schulzmc | Amazon Kindle | 165 | 01-23-2014 03:37 AM |
Disable Kindle Detection | Dark123 | Calibre | 6 | 12-15-2010 08:00 PM |
Possible to disable native PDF on Kindle with 2.3 | aa2300 | Amazon Kindle | 1 | 12-05-2009 01:59 PM |
Hacks how to disable usb charge of Kindle DX | Happen | Amazon Kindle | 4 | 09-19-2009 08:48 PM |
disable screen saver on Kindle DX | flyboyak | Amazon Kindle | 2 | 09-16-2009 01:39 PM |