From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [bluez-gnome] Authorization agent address-based whitelisting
Date: Tue, 07 Aug 2007 09:41:12 +0200 [thread overview]
Message-ID: <1186472472.20129.41.camel@violet> (raw)
In-Reply-To: <1186444253.10966.14.camel@sky.nicolast.be>
Hi Nicolas,
> 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.
did you ever tried bluez-gnome-0.13. You can know set the "trusted" flag
from preferences window and also during the authorization dialog.
Regards
Marcel
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-07 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 23:50 [Bluez-devel] [bluez-gnome] Authorization agent address-based whitelisting Nicolas Trangez
2007-08-07 7:41 ` Marcel Holtmann [this message]
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=1186472472.20129.41.camel@violet \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.