From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth clock and security manager
Date: Mon, 04 Apr 2005 14:38:23 +0200 [thread overview]
Message-ID: <1112618303.8263.92.camel@pegasus> (raw)
In-Reply-To: <312616200.24329@bjut.edu.cn>
Hi,
> I want to read local bluetooth clock with hcitool. But when I use the=
command "hcitool clock XX:XX:XX:XX:XX:XX=EF=BC=88local bd_addr)",the ret=
urn message is "not connected",and I am sure that I have created one ACL =
link.
> So, I use "hcitool clock XX:XX:XX:XX:XX:XX=EF=BC=88remote bd_addr)",=
the reture message is "read failed,Input/output error",but the command "h=
citool clkoff" works good.
the clock reading is a Bluetooth 1.2 feature. So make sure that you use
Bluetooth 1.2 device that supports this HCI command.
> There is another question about security mananger within BlueZ.
> I have paired my pda with BlueZ successfully,but I want to make it cl=
early that how to add authenticated device into the security manager in p=
rogramming ,and where do these authenticated device go?
The current security manager is inside hcid. The link keys are stored
at /etc/bluetooth/link_key.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-04-04 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 12:20 [Bluez-users] bluetooth clock and security manager Jin Pu
2005-04-04 12:38 ` Marcel Holtmann [this message]
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=1112618303.8263.92.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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