|
Anyone with Bluetooth want to test a scanner/logger I am working on?
I have recently gotten a pet project of mine to the level where I think it works well enough that other people can give it a shot, and I'm looking for some help in making sure it works as expected.
Basically, it is a Bluetooth scanner that is designed to do just one thing, scan for discoverable devices in range and record their MAC, name, and the time/date they were found to a log file. There are only a few options, it is pretty much a set it and forget it sort of thing. The only requirements are BlueZ (3.x or 4.x), and that your computer has a Bluetooth device that is supported by Linux. Obviously you will also need at least one device to scan for, and the more the better. If you want to take a walk through your mall while running it and seeing what you found, I would be ecstatic. A word of warning, I am not a very good C programmer and I have no doubt that there are mistakes in the code and improvements that could be made. To that end, if you have any suggestions, please let me know. You can download the source and get a little more specific information about it from: http://bluelog.digifail.com Any help would be greatly appreciated, thanks. |
Works great, just like you said. It picked up about 15 devices while I was walking around my house and logged everything correctly. (I have a lot of bluetooth stuff)
good luck, rabbit2345 |
That's a start, thanks.
Is this on the 64 bit SUSE in your profile, or a different distribution? |
It seems to work nicely on my rig (Slackware64 13.1). The only thing I had to do was set the march option in the makefile to x86-64 to get it to compile. It picked up my Android phone without a problem.
|
Yeah, I forgot to add any options for 64 bit in the makefile because I am on 32 bit, I'll fix that for the next version. Good to know it works on 64 bit machines though.
What kind of Bluetooth device were you using? Internal on a laptop, or a USB adapter? If you don't mind, the output of the following command would be helpful: Code:
hciconfig hci0 version |
It is internal on the laptop:
Code:
hci0: Type: BR/EDR Bus: USB |
Yup, works nicely on the netbook (Dell Mini 9) as well:
Code:
hci0: Type: BR/EDR Bus: USB |
To anyone who might be interested, I put an updated version up on the server today. A few small fixes, main additions are:
|
I have reached a new stable (probably) release of Bluelog, and thought I would bump this up a little bit for those who didn't see it. I have added a lot of options and fixed a lot of things since I posted last, but the main addition has been "Bluelog Live", a web front-end for Bluelog that could be used in a public area to raise awareness of Bluetooth security risks, much like the "Wall of Sheep" seen at DEFCON.
The interface can be skinned with CSS, and I have included two different versions, one based on my website's layout and another for BackTrack (which Bluelog will hopefully be included in someday): DigiFAIL BackTrack I understand the testing setup is kind of difficult for most people, since you need not only a Linux box with Bluetooth hardware but at least a few devices to scan, but I would appreciate anyone who could give the new version a try and see how it works out on different distributions/setups. Even if you can only scan one device with it, it is enough to show it works. |
I didn't test the Bluelog Live bit, but the basic program works just fine. It complies on my 64 bit machine and finds all the bluetooth devices in the area.
|
Well, it is good to know it is building properly on other architectures now. The first versions used a makefile that was basically just for testing, now I am using a proper (well, better) makefile that should work right on all systems and has install/uninstall targets (which I needed for Live anyway).
Much thanks for your continued help. |
| All times are GMT -5. The time now is 01:54 AM. |