Home

Richard

Sly blue is a simple program that monitors bluetooth connections in your vicinity. You supply a list of known devices via their hardware address and user defined device name along with a script to run and a timeout value. It should be noted this version does not pair with any device. It simply waits for a device to show up. Some devices need to be discoverable in order for them to show up. This program isn't meant to be totally secure. My reasoning for this was to open some firewall ports and turn on some lights when I arrive home. With this in mind please take caution on what you use this program for. I would not suggest using it to unlock your machine.

All unknown connections and devices are logged. If there is something out of the ordinary I default to exiting the program. I also check for modifications of the shell scripts that are ran automatically.

The program consists of only a daemon called slyblue.
The default files that are installed:
/etc/slyblue/slyblue.conf --Main configuration file
/etc/slyblue/example.sh -- An example shell script
/usr/local/sbin/slyblue -- The Sly blue program

The slyblue configuration file is a tab delimited file. Please see the default configuration file for an example.

The example shell script is a shell that can be used to create your own script. While the name of the file can be anything and can do what ever you want, it requires the ability to take two arguments. Which are "start" and "stop". This is based on /etc/rc scripts and any rc file should work.

You may modify the Makefile to your preferences too. You can change the configuration file name and location. The default path to search for the shell scripts and you can change the log file location.
To keep this small I didn't generate any configure scripts. If it fails, the only Library that you may need to define is the Bluez library.

The default polling time is defined in the configuration file.

A couple of debugging options are also available. Run slyblue --help for those options.

The program is designed to work with Linux and the Bluez bluetooth stack.

A few other things to mention
1. Make sure to turn up your interface. hciconfig hci[Device #] up
2. The bluetooth inquiries made by this program are not passive.

Good luck and enjoy...