Bluetooth Hacking?
Datamining 23C3

From OpenBeacon

Jump to: navigation, search


Actually - as the author of this page - I wouldn't mind some feedback (of any kind) from somebody (maybe the fathers of openbeacon) on the feedback page? Thx!

This all assumes that one log-stanza is 24 byte (btw - have fun by searching for the flaw in 
log-2006-12-27-13 - which has originally 4.115.960 bytes, which is 171498,3333 if you divide 
it by 24).
Here some findings about the Sputnik project: 

mysql> select count(*) from log1;
 ---------- 
| count(*) |
 ---------- 
| 11144232 |
 ---------- 
1 row in set (0.00 sec) 
 

mysql> select count(*), sip from log1 group by sip;
 ---------- ----------- ----------- 
| count(*) | sip       | sip_form  |
 ---------- ----------- -----------  

129144	184418311	10.254.0.7
8524	184418404	10.254.0.100
187078	184418558	10.254.0.254
448760	184418565	10.254.1.5
758782	184418566	10.254.1.6
568765	184418567	10.254.1.7
532699	184418572	10.254.1.12
570525	184418576	10.254.1.16
494524	184418582	10.254.1.22
1322696	184418819	10.254.2.3
428565	184418821	10.254.2.5
563488	184418826	10.254.2.10
760606	184418828	10.254.2.12
231483	184419077	10.254.3.5
376396	184419081	10.254.3.9
130379	184419085	10.254.3.13
54863	184419093	10.254.3.21
171311	184419334	10.254.4.6
528187	184419339	10.254.4.11
589640	184419340	10.254.4.12
596466	184419586	10.254.5.2
880833	184419605	10.254.5.21
225075	184420110	10.254.7.14
585443	184420366	10.254.8.14 

24 rows in set (4 min 23.80 sec)
If you are wondering why the accesspoints differ from the one on 
http://openbeacon.org/dl/23C3/locations_a.csv _b.csv and _c.csv (details 
http://www.openbeacon.org/downloads.0.html ), ask the authors. maybe sb should 
tell them about maintaining and updating standards?

Some other interesting findings:

select sOid, count(*) from log1 group by sOid
 ---------- ----------- 
| count(*) | soid      |
 ---------- ----------- 
|   179090 | 269942784 |
|   556588 | 269942869 |
|  1144585 | 269942954 |
|  9050534 | 269943039 |
|     3784 | 269943296 |
|    11825 | 269943381 |
|    22702 | 269943466 |
|   175124 | 269943551 |
 ---------- ----------- 
8 rows in set (1 min 40.39 sec)

If sb can point me to my error here, I would greatly appreciate that.

Same goes for the following two:

mysql> select distinct sseq from log1;
 ----------- 
| sseq      |
 ----------- 
| 184419077 |
| 184418572 |
| 184419605 |
| 184419339 |
| 184419093 |
| 184420110 |
| 184418566 |
| 184418819 |
| 184418567 |
| 184418826 |
| 184418565 |
| 184418582 |
| 184418821 |
| 184418828 |
| 184419085 |
| 184419334 |
| 184418558 |
| 184418311 |
| 184420366 |
| 184419340 |
| 184419586 |
| 184419081 |
| 184418404 |
| 184418576 |
 ----------- 
24 rows in set (0.00 sec)

mysql> select distinct sstrength from log1;
 ----------- 
| sstrength |
 ----------- 
|        65 |
 ----------- 
1 row in set (37.40 sec)

All entries with the same strength?
Talk and article from 24C3 describing reconstruction of lost sequences from 23C3:
http://events.ccc.de/congress/2007/Fahrplan/events/2270.en.html

Web page with attempts of rebuilding missing IDs: http://www.bogomips.w.tkb.pl/sputnik.html