Hi Michael, Chris, sorry to step into this conversation way too late. I changed my job last year's summer and bought a house too. So it's no wonder I had little time afterwards to move back to development on blueproximity. It is true that I use LP now to track things like this. I can confirm the bug you described above. Making it more responsive is not possible since bluetooth itself defines some parts here. Proximity checking intervals can be done only once per second and there is some algorithm behind the link quality detection inside the bluetooth stack which also gives slower reaction (normalization seems to take place there). Possible ways to fix this: reduce the lock time and distance. If you leave your computer unlocked, move slower :-).
Generally it is no total security tool, it can be used in many creative ways. Locking is just the most obvious one. It is an extra security but you should not rely on it sorely. Please keep locking your computer manually too. Unlocking via blueproximity still works. The other part is creating a daemon, I like the idea and it is on my list for blueproximity 2.0 (which itself is on the list for things to-do during the next 12 months but it has no priority at the moment) Idea list includes: - using a daemon for proximity checking - using a user part for executing the commands (I cannot see a good (secure) way to have the commands be executed as the user other than this daemon) - more devices to be scanned - more events per device to be detected - preset of commands (via plugin mechanism) to be executed - setting up command chains via gui only - keeping it simple enough to still work and look good and being usable by standard users At the moment I am busy with work, family, house and in the sparetime I build a media pc for my mother, creating a nice complete remote control for an ipod touch for mythtv. I know there are some but none of them works as my mother would expect. -- blueproximity can be bypassed to not force a lock https://bugs.launchpad.net/bugs/286820 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
