From: Marcel Holtmann <marcel@holtmann.org>
To: Nosve <nosve@libero.it>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Pairing to devices with bluez and widcommwithsame adapter
Date: Fri, 23 Jan 2004 17:15:01 +0100 [thread overview]
Message-ID: <1074874501.3071.132.camel@pegasus> (raw)
In-Reply-To: <AGELIJDLJNOPFNMOHHIFAECLCAAA.nosve@libero.it>
Hi Nosve,
> I don't want to be pedantic, but the question is how to store the link key
> in the chip, I must use hcitool to send some form of commands? Or maybe
> there are some documented possibilities which I have not found?
the support for stored link keys is not very good. You must write it by
your own. The code of the new library also have no tool for it at the
moment, but the API call is there.
> Even from the other thread I don't understand if maybe we must hope there is
> a possibility to save the link key with widcomm stack.
If the link key is stored on the chip, the host stack don't have to do
anything. All authentication stuff will be handled by the link manager.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-01-23 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 17:21 [Bluez-users] Pairing to devices with bluez and widcomm with same adapter Nosve
2004-01-22 22:20 ` Marcel Holtmann
2004-01-23 9:30 ` R: [Bluez-users] Pairing to devices with bluez and widcomm withsame adapter Nosve
2004-01-23 13:38 ` Marcel Holtmann
2004-01-23 15:58 ` R: [Bluez-users] Pairing to devices with bluez and widcommwithsame adapter Nosve
2004-01-23 16:15 ` 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=1074874501.3071.132.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nosve@libero.it \
/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