From: Nicolas Trangez <eikke@eikke.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [bluez-gnome] Authorization agent address-based whitelisting
Date: Tue, 07 Aug 2007 01:50:53 +0200 [thread overview]
Message-ID: <1186444253.10966.14.camel@sky.nicolast.be> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 646 bytes --]
Hija,
I'm working on bluetooth mouse handling in the GNOME desktop recently.
Now I finally got my mouse working (took a while), I could get some
coding done. As part of this I thought it could be useful to get around
the passkey agent authorization question for some devices (ie mouses),
without enabling auto_authorize in the bluetooth-applet configuration.
Attached you can find a patch to auto-grant authorization request for
some devices based on their BT address. The addresses are stored in
gconf as a simple list of strings.
The preferences editor has not been altered (yet) to manipulate this
list.
Thanks,
Nicolas
[-- Attachment #1.1.2: 0001-Automatic-authorization-whitelisting.patch --]
[-- Type: application/mbox, Size: 4626 bytes --]
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-08-06 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 23:50 Nicolas Trangez [this message]
2007-08-07 7:41 ` [Bluez-devel] [bluez-gnome] Authorization agent address-based whitelisting Marcel Holtmann
2007-08-07 12:04 ` Nicolas Trangez
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=1186444253.10966.14.camel@sky.nicolast.be \
--to=eikke@eikke.com \
--cc=bluez-devel@lists.sourceforge.net \
/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