[Windows Mobile Development and Hacking General] SevenRains:
[Documentation]

In this documentation I will refer to the screenshots in the initial post. If you look at the tabs at the bottom you'll see four of them: "Scan", "Jack", "Script" and "Track". I'll try to walk you through all of those step-by-step since currently there is no documentation.

Scan

This is the main tab of Whiskers. It will not only scan for devices whether Bluetooth or Wireless but you will also be able to do various things with the found devices.

For a quick start, your bluetooth and/or wireless adapter has to be switched on. Whiskers doesn't do this for you and should fail silently if it doesn't find the adapter turned on.

Then you can just hit the Scan button and Whiskers will start to scan for devices or access points around you.

You can press "Clear" to flush current found devices or press "Delete" to remove individual devices from the list. Naturally, if Whiskers is scanning it will probably find the device again.

The input box right next to the Start button is the scanning time interval measured in milliseconds. That is, the time for which Whiskers will pause between scanning. You can set it at your convenience but 1000ms (1s) is quite a good value.

The Open / Save buttons you can use to open a saved list or store a saved list.

Let's move on to the Comm tab.

Comm

This tab is meant for communicating with other users using Whiskers. Although it's only based on bluetooth and hence the short range, it may come in handy when other Whiskers features will be implemented.

To communicate with a device, first make sure you've scanned it using the Scan tab, enter your message in the box below and click Send. If the other device is using Whiskers and is in listening mode, after a couple of tries your message should appear on your screen and on the other device's screen.

To receive messages, you must have clicked the Start Listening button which will make Whiskers listen to all incoming messages.

And now the Jack tab.

Jack

This tab is meant for jacking / autojacking. I have some development ideas which I won't divulge just yet but for the time being only this form of eh... annoyance is possible. The whole concept started from quite an old java applet I used to have on my mobile phone... You could set it to jack a message continuously and you'd just stroll around and it would jack any device which came in range.

To jack a device (only bluetooth devices, of course) you select a device in the Scan tab, then select the Jack method, either pairing or file, enter your message (the shorter the message the better!) and press the Jack button.

To autojack, you enter your message and and select a jacking logic (rotation - Whiskers will rotate in a round-robin fashion going through all devices, first in - Whiskers will jack any "new" device it finds, random - Whiskers will randomly select devices from the Scan tab) and press the Start AutoJack button. If you switch to the Scan tab you will see which device Whiskers is currently jacking. The time to live (TTL) is how much Whiskers will wait for a timeout while jacking a device (10 000ms, 10 seconds should give enough time to properly jack a device).

Please use this feature responsibly :-) Let's move on to the Script tab.

Script

The purpose of this feature is to execute certain commands when a specific device is detected. You can search for a specific address, device name, type of device (the drop down boxes will help you choose), and whether it should be a BT (Bluetooth) device or an AP (access point).

To add a script, you may choose to fill any or none of the filters. You can search for a device name... Or maybe just a device class... Then you write or browse for an executable and fill in any optional parameters and click Add. You can later add the script by just clicking the script in the big box.

The next step is to enable scripts by clicking the Enable Scripts button. The time frequency (in milliseconds) is how often the scripts will trigger on the devices it finds.

That's it for the Script tab.

Track

Uh. This is a difficult one. The Track tab, given you have a GPS device, will log at what latitude and longitude it found a device. It will store this in a GPX file along with the device name and device address. Optionally, of course, once you've gathered some data, you may choose to press the Upload button which will upload the GPX file to a central server [I'll explain this more in the next post]. Given that some user spotted a specific device and has uploaded it to the server, you can search for devices using the search feature. This will place dots on the map [They may be hard to see on the default map, and I'm sorry for this, I'm still searching for solutions] at the respective locations. You can then choose to save the map with the dots using the Save button or you can clear all the dots by pressing the Reset button.

[Considerations]

You can use the program to scan for devices continuously. I used it to track around and discover what devices people are using. Needless to say that some had quite funny names or just adverts. I also picked up a TomTom device from a car. It's quite interesting and does fulfill some voyeuristic pleasure I guess. It's impressive though how many devices I've found... Tons of them, pages and pages of scrolling.

You can use the program to jack devices eh... In an educational manner, of course. Or to autojack while Whiskers discovers new devices. Please don't over-abuse it since it can be pretty annoying. In comparison to btCrawler or Bloover or whatever, Whiskers is meant to be the first tool before you use any of those. Bluesnarfing on newer devices is quite possible IF and only IF the user has accepted to pair with you. From then on, you could use one of those nifty tools which grant you access to all the cool and nasty features. I've seen a lot of discussion about being able to snarf without the user having to accept the pairing and, from what I've seen, sadly there is no such tool. Whiskers will try to get you paired but development in this department is halted for the time being.

The tracking feature currently uses my personal server. In time, when things get more stable I'll also publish the server-side part of Whiskers so you can make your own server (I have to, this is OpenSource). Of course, the search feature is only useful if you have a big enough database. It will also be possible to add your own maps rather than the default map.