public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Pall Thayer <palli@pallit.lhi.is>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] accessing info on paired devices
Date: Tue, 28 Sep 2004 10:43:29 +0200	[thread overview]
Message-ID: <1096361009.4684.36.camel@notepaq> (raw)
In-Reply-To: <415921D4.9000605@pallit.lhi.is>

Hi Pall,

> But the link key is in binary form so I can't read it. What I've been 
> doing is just sending a single l2ping to each of the discovered devices, 
> the ones that are paired and authorized respond, the others time-out and 
> are eventually ignored. The only problem is that I end up with a stack 
> of PIN request pop-ups for the ones that aren't paired and authorized. 
> Not a big deal but somewhat annoying. I tried playing around with the 
> security settings in hcid.conf but nothing I did managed to avoid the 
> PIN request pop-up.

we will change the link key file to be ASCII, but you should understand
the three security modes of Bluetooth. I think you put your device into
security mode 3 and this is bad unless you really know what you are
doing.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-09-28  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 18:34 [Bluez-users] accessing info on paired devices Pall Thayer
2004-09-28  8:16 ` Marcel Holtmann
2004-09-28  8:33   ` Pall Thayer
2004-09-28  8:43     ` 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=1096361009.4684.36.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=palli@pallit.lhi.is \
    /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