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:31:06 +0200 [thread overview]
Message-ID: <1114515066.10706.204.camel@pegasus> (raw)
In-Reply-To: <2621d9af0504260302e1c13c7@mail.gmail.com>
Hi,
> I ran a test with the new configuration and found out the bluetooth
> devices which has this config modified accepted any device coming. The
> pairing window is not poped up anymore, but the link_key is not
> updated (still 0 byte).
>
> As my understanding, this config ignores the pairing and pin code. It
> accepts all devices connecting to my device, no authentication. Is
> that it?
check the Bluetooth specification and understand the differences between
the security modes. Use only security mode 3 if you really know what you
are doing. Otherwise use the service level security features of L2CAP
and RFCOMM.
> What I want is to avoid the pin popup for certain bluetooth devices
> (know specific BD_ADDR). When those allowed devices connect to my
> device, then I will try to provide "silently" the PIN (no popups) and
> the pairing should be done from there. If other device which BD_ADDR
> does not belong to the list of addresses that my device has, it should
> not be rejected.
If you wanna do that with the bluez-utils prior 2.16 you need to write
your own PIN helper program. With 2.16 you can use a pincodes file for
these task.
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
next prev parent reply other threads:[~2005-04-26 11:31 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
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 [this message]
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=1114515066.10706.204.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