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

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.

Pall

Marcel Holtmann wrote:
> Hi Pall,
> 
> 
>>I'm working on a little project that would have to automatically scan 
>>for bluetooth devices (using a little perl script) and then attempt to 
>>connect to them. However, I would prefer if it would only attempt to 
>>connect to devices that have already been paired with the computer (via 
>>bluetooth usb-dongle) and ignore discovered devices that have not been 
>>paired. So, how can I find out which of the discovered devices have been 
>>paired?
> 
> 
> if there exists a link key for this device then they are paired, but the
> problem is that security mode 1 not demands to pair two devices.
> 
> Regards
> 
> Marcel
> 
> 

-- 
_______________________________
Pall Thayer
artist/teacher
http://www.this.is/pallit
http://pallit.lhi.is/panse
_______________________________

  reply	other threads:[~2004-09-28  8:33 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 [this message]
2004-09-28  8:43     ` 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=415921D4.9000605@pallit.lhi.is \
    --to=palli@pallit.lhi.is \
    --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