From: Scott James Remnant <scott@netsplit.com>
To: linux-bluetooth@vger.kernel.org
Cc: keybuk@chromium.org, Scott James Remnant <scott@netsplit.com>
Subject: [RFC PATCH 0/2] auto-pairing plugin
Date: Fri, 20 Jan 2012 17:59:55 -0800 [thread overview]
Message-ID: <1327111197-11446-1-git-send-email-scott@netsplit.com> (raw)
A few core changes here to support retrying of connections without
losing the original connection request, temporary D-Bus device object
or Agent information - and plugin callbacks for when bonding is
complete and cancelled.
This lets us implement an auto-pair plugin that tries the PIN 0000 for
commonly dumb devices, and retries using the Agent when that PIN fails.
For added cutesyness we save the blacklist we use to avoid repeatedly
sending 0000, so if there really are any devices out there with
different default PINs we can learn about them over time.
Net effect - another thing done in the UI Agent moved into bluetoothd
where it belongs.
*** BLURB HERE ***
Scott James Remnant (2):
plugin: add bonding complete and cancel callbacks with optional retry
autopair: add autopair plugin
Makefile.am | 5 +
acinclude.m4 | 6 ++
plugins/autopair.c | 209 ++++++++++++++++++++++++++++++++++++++++++++++++++++
src/adapter.c | 2 +-
src/device.c | 86 +++++++++++++++++++++
src/device.h | 12 +++
6 files changed, 319 insertions(+), 1 deletions(-)
create mode 100644 plugins/autopair.c
--
1.7.7.3
next reply other threads:[~2012-01-21 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:59 Scott James Remnant [this message]
2012-01-21 1:59 ` [RFC PATCH 1/2] plugin: add bonding complete and cancel callbacks with optional retry Scott James Remnant
2012-01-21 1:59 ` [RFC PATCH 2/2] autopair: add autopair plugin Scott James Remnant
2012-01-23 14:28 ` [RFC PATCH 0/2] auto-pairing plugin Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327111197-11446-1-git-send-email-scott@netsplit.com \
--to=scott@netsplit.com \
--cc=keybuk@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).