Linux bluetooth development
 help / color / mirror / Atom feed
From: "Nosve" <nosve@libero.it>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ Mailing List" <bluez-users@lists.sourceforge.net>
Subject: R: [Bluez-users] Pairing to devices with bluez and widcommwithsame adapter
Date: Fri, 23 Jan 2004 16:58:17 +0100	[thread overview]
Message-ID: <AGELIJDLJNOPFNMOHHIFAECLCAAA.nosve@libero.it> (raw)
In-Reply-To: <1074865136.3071.125.camel@pegasus>

Hi Marcel

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?
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.

Thanks for your patience

> -----Messaggio originale-----
> Da: Marcel Holtmann [mailto:marcel@holtmann.org]
> Inviato: venerdì 23 gennaio 2004 14.39
> A: Nosve
> Cc: BlueZ Mailing List
> Oggetto: Re: [Bluez-users] Pairing to devices with bluez and
> widcommwithsame adapter
>
>
> Hi Nosve,
>
>
> You only have to store the link key once on the chip and you never have
> to care about the authentication procedure again. Decide by yourself
> what place is safer. The dongle or your harddisk.
>
> Regards
>
> Marcel

  reply	other threads:[~2004-01-23 15:58 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       ` Nosve [this message]
2004-01-23 16:15         ` [Bluez-users] Pairing to devices with bluez and widcommwithsame adapter Marcel Holtmann

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=AGELIJDLJNOPFNMOHHIFAECLCAAA.nosve@libero.it \
    --to=nosve@libero.it \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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