sensepost / snoopy-ng

Snoopy v2.0 - modular digital terrestrial tracking framework
Other
429 stars 128 forks source link

Bluetooth #62

Open keldnorman opened 8 years ago

keldnorman commented 8 years ago

A way to dodge the sniffing of a bluetooth scanning is to use a special char in the presented name from the bluetooth client (in my case my phone) - notice the "\u2714" below from the snoopy.log

2015-08-23 09:30:49 ^[[31m!!^[[32m snoopy: Exception whilst trying to insert data, will sleep for 5 seconds then continue. Exception was: ^[[31m'latin-1' codec can't encode character u'\u2714' in position 12: ordinal not in range(256)^[[32m 2015-08-23 09:30:49 ^[[31m!!^[[32m snoopy: Offending table: bluetooth_details 2015-08-23 09:30:50 ^[[31m!!^[[32m snoopy: Data: [{'name': u'Kelds Phone\u2714 ', 'run_id': 1908442348, 'classType': 'Phone, Smart phone (0x7a020c)', 'manufac': 'Unknown', 'mac': '133713371337', 'lmpVer': 'Unknown'}] 2015-08-23 09:30:54 D blutooth.py: Scanning for bluetooth devices 2015-08-23 09:30:55 D snoopy: Not syncing table 'bluetooth_details' - no 'sunc' column

Just a FYI :)

keldnorman commented 8 years ago

Unless..

You start snoopy with the db connect string + "?charset=utf8" ref the posting here: https://github.com/sensepost/snoopy-ng/issues/42

Then It works when I start my snooping with this line:

/usr/bin/snoopy --dbms=mysql://snoopy:supersecretpassword@127.0.0.1:3306/snoopy?charset=utf8 --flush --drone Drone --location Denmark -m gpsd:freq=30 -m blutooth -m heartbeat -m sysinfo --plugin wifi:iface=mon0,mon=True -m rogueAP:ssid=Internet --server=http://10.8.0.1:9001/ --key=IAM1DRONEKEY --verbose

Looking in the MySql database under the bluetooth_details table I now see the correct string :o)

133713371337 Kelds Phone✔ Phone, Smart phone (0x7a Unknown Unknown 1953092142

/K