Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] auto pairing between client & server
Date: Tue, 26 Apr 2005 13:28:40 +0200	[thread overview]
Message-ID: <1114514920.10706.201.camel@pegasus> (raw)
In-Reply-To: <2621d9af05042603075410e639@mail.gmail.com>

Hi,

> Thanks for replying. I'm using an old version of BlueZ stack, which
> link key file is a binary file. I know we have a new thread talking
> about changing this file to ascii. Since my product is already in
> development phase, I can't wait until the new BlueZ release coming out
> to use that feature.

actually there should be no problem to upgrade, because nobody
complained about any problems so far.

> Do you know any tool that can go and extract the content of the link
> key file from binary to readable format ascii? (That's how I should
> verify the pairing state in the link key file, right?)

With an easy answer, yes. If you have a link key, then you are paired.
However I don't know of any tool that extracted the binary link key file
format to an ASCII based version.

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

  reply	other threads:[~2005-04-26 11:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 20:06 [Bluez-users] auto pairing between client & server N. I.
2005-04-22 21:38 ` Marcel Holtmann
2005-04-24 16:17   ` Fredy P
2005-04-25 14:26     ` N. I.
2005-04-26 10:07   ` N. I.
2005-04-26 11:28     ` Marcel Holtmann [this message]
2005-04-23 21:31 ` Marco Trudel
2005-04-25 14:29   ` N. I.
2005-04-25 14:38     ` Marco Trudel
2005-04-26 10:02       ` N. I.
2005-04-26 10:44         ` Marco Trudel
2005-04-26 13:39           ` Marcel Holtmann
2005-04-26 11:31         ` Marcel Holtmann
2005-04-26 17:37           ` Marco Trudel
2005-04-26 17:46             ` Marcel Holtmann
2005-04-26 18:36               ` Marco Trudel
2005-04-26 19:04                 ` Marcel Holtmann
2005-04-26 22:31                   ` N. I.
2005-04-27  8:44                   ` Marco Trudel
2005-04-27  8:50                     ` Marcel Holtmann
2005-04-27  8:54                       ` Marco Trudel

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=1114514920.10706.201.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