From: Rusev <arusev@dev.rtsoft.ru>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] hcid to passkey agent interaction question
Date: Fri, 09 Nov 2007 19:14:40 +0300 [thread overview]
Message-ID: <47348770.5030509@dev.rtsoft.ru> (raw)
Greetings!
>>From my experiments with pairing to various devices I found that
presence of pincodes file (in /var/lib/bluetooth/<dondle-MAC>/) in mode
"user" prevents
from pairing for some unknown reason, while absense
of pincodes file in mode "auto" just makes hcid fallback
to using of D-bus passkey agent.
Is it intented behavior? I suggested that in "user" mode pincodes would
be ignored...
Im using BlueZ libs/utils ver. 3.22
Regards,
Alexandre.
-------------------------------------------------------------------------
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
reply other threads:[~2007-11-09 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47348770.5030509@dev.rtsoft.ru \
--to=arusev@dev.rtsoft.ru \
--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;
as well as URLs for NNTP newsgroup(s).